| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds an optional argument to rotate the skyview display, making
it possible to orient it correctly based on the direction one is
actually facing. The specified heading is positioned at the top.
This edit does not update contrib/webgps.py, which is somewhat
more complicated to fix due to the Javascript involvement.
TESTED:
Ran both programs with and without the -r or --rotate option.
Signed-off-by: Gary E. Miller <gem@rellim.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In some cases, the elevation and azimuth information are missing
(i.e., reported as 0) for some satellites. E.g., the Navika-100
receiver fails to report positions for SBAS satellites. This change
avoids showing such satellites at the "north point" of the display.
They are *not* excluded from the textual list.
TESTED:
Ran xgps, xgpsspeed, and webgps.py against data from a Navika-100
receiver, and verified that the SBAS satellites are no longer
inappropriately shown at the top.
Signed-off-by: Gary E. Miller <gem@rellim.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Although this isn't strictly a Python 3 requirement, using the
new-style class definition syntax improves consistency between Python
2 and Python 3. Old-style classes have been deprecated since Python
2.2, but many such definitions linger on. Python 3 eliminates
old-style classes, but instead of complaining about old-style
definitions, it simply unconditionally and silently makes all classes
new-style. The only incompatible differences are quite subtle and
rarely matter in practice, but things are more consistent across
versions if the new-style definitions are used.
Also, the preferred method for subclasses to invoke parent init
methods is via the super() construct, which is only available with
new-style classes. Using super() is especially useful with multiple
inheritance, which it handles automatically (provided that the init
methods have compatible signatures).
TESTED:
Using an SConstruct patched to run the build helpers with the target
Python, ran "scons build-all check ", as well as gpsprof and xgps,
with all six supported Python versions (except 2.6 for xgps).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This makes the "future import" statements consistently specify
absolute_import, print_function, and division, for maximum consistency
between Python 2 and Python 3. Although absolute_import is probably a
don't care for top-level programs, if unit tests were ever implemented
for the programs they would be imported as modules, making the module
import behavior relevant.
Note that previous Python 3 fixes are a prerequisite for this change.
Also makes the "polyglot comment" consistent across sources.
TESTED:
Using a version of SConstruct patched to use the target Python for
build helpers, ran "scons build-all check valgrind-audit
www/hardware.html" with all six supported Python versions. Also ran
gegps, gpscat, gpsprof, xgps, and xgpsspeed with both Python 2 and
Python 3.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This changes a few integer division cases to use the '//'
floored-division operator, matching the normal Python 2 (C-like) '/'
behavior, for compatibility with the switch to the "mathematical"
divison operator in Python 3 (and in Python 2 with the "future
division" import). This was more about keeping the behavior the same
than determining whether floored division is actually the proper
choice.
One place where floored division is definitely wanted is in the GPS
week calculations in leapsecond.py, which are now OK for Python 3,
though currently that module is only used by SConstruct, and hence not
with Python 3.
Two other minor fixes:
1) The GPS base date is corrected in the comment in leapsecond.py.
2) The fit_to_grid() function in xgps now consistently returns floats,
rather than returning either ints or floats depending on the line
width.
TESTED:
Ran "scons build-all check" with all 6 supported Python versions.
Also ran xgps and xgpsspeed with all but 2.6.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since the radio-button labels in the add_ui_from_string() text are
just internal labels not visible to the user, there's no reason that
they need to rely on non-USASCII characters. With that text confined
to 7-bit ASCII, there's no need to use Unicode for the literal, which
in turn eliminates the last incompatibility with Python 3.2. Note
that this isn't the only case where the internal labels mismatch the
user-visible text (the other ones involve embedded blanks).
The fact that Gtk3 assumes 'ascii' for the encoding in this case may
actually be a bug.
TESTED:
Ran xgps with Python 2.7 and 3.2-3.5 (using appropriately built
extensions).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The Gtk MessageDialog function gives a warning if no parent window is
specified. Since the main window already exists in those cases, it's
simply a matter of passing the extra argument to MessageDialog.
This has the side effect of changing the position of the dialog box,
such that it's centered over the parent window rather than being near
its upper left-hand corner. In the xgps case, it appears to be
centered over whichever subwindow was most recently updated.
TESTED:
Verified that both the gpsd not running and gpsd stopped running cases
no longer produce warning messages on the terminal.
|
|
|
|
|
|
|
|
|
| |
This replaces the obsolete 'cmp' keyword for 'sorted' with the
still-available (and more efficient) 'key' keyword.
TESTED:
Ran xgps with Python 2.7, 3.3, 3.4, and 3.5 (with appropriate
builds).
|
|
|
|
|
|
| |
TPV has field status only when STATUS_DGPS
Signed-off-by: Gary E. Miller <gem@rellim.com>
|
|
|
|
|
| |
Also update the affected regression files. gpsd had been
throwing away the DGPS status.
|
| |
|
| |
|
|
|
|
| |
...change their shebang lines to plain Python.
|
| |
|
|
|
|
|
|
|
| |
Removes a dependency on the deprecated gobject/pygtk bindings.
Note: this leaves build.txt out of date. To be fixed when we deal with
xgpsspeed.
|
|
|
|
| |
Also, set xgps back to requiring python2 because of the gobject problem.
|
| |
|
|
|
|
|
|
| |
For the moment most shebang lines still say 'python2' rather than just 'python'.
This is because the client code in gps/ hasn't been touched yet; the internal
imports break under Python 3 and that needs to be fixed.
|
|
|
|
|
| |
large scale autopep8 cleanup of several
pep8 whitespace warnings
|
|
|
|
|
|
| |
We've learned that Ubuntu 15.10 will have python3 as default. The ugly
transition gas befun; our only recourse is to hape that all our deployment
targets have 'pyton2' do the right thing. Works on 14.10.
|
|
|
|
|
| |
Before this fix, satellites from the Beidou or QZNSS wuld have been
incirrectly displayed with the SBAS shape.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
spaces around operators
no extra spaces around parameter binding assignments
spaces around = for assignment
normalized whitespace between functions and classes
indentation normalization
two spaces before a comment # and one space after it
Should be no actual code changes just stylistic cleanup for readablity
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Signed-off-by: Eric S. Raymond <esr@thyrsus.com>
|
| |
|
|
|
|
| |
Signed-off-by: Eric S. Raymond <esr@thyrsus.com>
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This avoids coredumps in case DISPLAY is not usable.
See http://bugs.debian.org/602925 for details.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Only one device is known to generate them, and they clutter the display
badly for the others.
|
| |
|
| |
|
| |
|
|
|
|
| |
Signed-off-by: Eric S. Raymond <esr@thyrsus.com>
|
|
|
|
|
|
|
|
| |
Protocol version number is bumped. Python and C test clients are known
to work; interfaces of the C and Python client bindings are
unchanged. Third-party client-side bindings which rely on naively
copying JSON members will break (implementers have been repeatedly
warned not to do this).
|
| |
|