| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* doc/comments: fix typo: chosen not choosen
* doc/comments: fix typo: truncated not trucated
* doc/comments: fix typo: unknown not unkown
* doc/comments: fix typo: attribute not atribute
* doc/comments: fix typo: Convenience not Convinience
* doc/comments: fix typo: forbidden not forbiden
* doc/comments: fix typo: government not goverment
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Fixes displaying the heightline route info
* Use cached copy for libpng / tomtom (#276)
* Update build_tomtom_plugin.sh
* Update build_tomtom_minimal.sh
* Renamed the Links to fit navit repo
|
| |
|
|
|
|
|
|
| |
New filter entry "Bus&Train" for the POI menu of the internal GUI,
to show only bus stops and train stations.
Useful for finding nearby public transport options.
|
|
|
|
| |
Since getenv may return NULL if a variable is not set, current keyboard
code crashes if LANG environment is not set.
|
|
|
|
|
|
|
|
|
|
| |
* Add network info menu in gui/internal for Linux
* Ensures that ifaddrs.h is available before enabling network info code
* Add network info to sailfish config as well
* Prevent linker and undefined reference errors for non-unix builds
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When deactivating vehicle, profile is choosen from "car" vehicle_profile or by
default the first vehicle_profile in list. So, by example,
car_avoid_tolls never work when manually selecting current position (and
deactivate vehicle).
Now, if there is a selected vehicle profile, we keep it as
vehicle_profile (not changing it).
Aditionnaly, in internal gui, selecting a vehicle profile when wehicle
is deactivated, in gui_internal_cmd_set_active_profile(), call navit_set_vehicleprofile_name() with new
vehicle_profile (by name) before setting vehicle_attr to NULL (like in
gui_internal_cmd_set_position()).
Now, we can switch profile when vehicle is deactivatied and route is
update correctly.
TO DO : Same in other gui
TO TEST : with more than one vehicle enable
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
possible ones (leftover from PR5) (#210)
* Add:gui_internal:In search, hide on-screen keys which will not find a result.
During incremental search in the search dialog, hide keys on the
on-screen keyboard which will not lead to any search result.
Before, keys where highlighted if they would lead to a result.
* Remap special characters in Search to standard characters to enable useful hide-key-functionality
* Fix highlight (hide) possible next keys for search internal
Now only shows possible keys, not the nth key of the searched item. Takes care of umlauts.
* Add a switch attr for gui internal to decide to use hide_keys or the old highlight key behaviour
usage: add the attr 'hide_next_possible_keys="1"' to <gui type="internal" [...] />
|
|\
| |
| |
| |
| |
| |
| | |
Conflicts:
navit/Makefile.am
navit/xpm/Makefile.am
po/Makefile.am
|
| |
| |
| |
| |
| |
| |
| | |
Use the term 'category' for all plugins with the same API (GUI plugins,
map plugins etc.). This used to be called 'type', which was confusing,
because in the XML config, 'type' refers to what is called 'name' in the
code.
|
| | |
|
| |
| |
| | |
show a notification in heightprofile when no map is found providing heightlines
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
results"
This reverts commit 53b333a617146bc304063f8ddd0dfe2927bb6064.
That commit made POI filtering behave unexpectedly, returning empty result
sets sometimes. I was able to reproduce it on x64 linux in following way:
start POI filtering, then press "POIs" on the top to return to POI list,
then press looking glass to start POI filter once again.
I was unable to get non-empty results on my Android device.
It also has introduced some valgrind warnings about accessing an already freed
location after query text is entered and actual search is fired.
Hope @mvglasow will take a closer look on this issue.
|
| |
| |
| |
| |
| |
| | |
Do the automatic switch in gui_internal_keypress_do instead of
gui_internal_search_changed so that other text input widgets would benefit,
e.g. poi search.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
During table rendering, do not disable off-screen table entries by
toggling STATE_SENSITIVE. Doing so breaks the menu items "Set distance to"/
"Get more"; these must never be STATE_SENSITIVE, since their sub-widgets
should receive clicks.
Instead, use STATE_OFFSCREEN to mark off-screen entries and skip them
during traversal with a rotary encoder.
|
| | |
|
| | |
|
| |
| |
| |
| | |
Signed-off-by: mvglasow <michael -at- vonglasow.com>
|
| |
| |
| |
| | |
Signed-off-by: mvglasow <michael -at- vonglasow.com>
|
| |
| |
| |
| | |
Signed-off-by: mvglasow <michael -at- vonglasow.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Allow graphics plugin to specify size occupied by keyboard
Create placeholder for Android keyboard
Show Android keyboard in landscape mode
Skip keyboard logic if hardware keyboard is present on Android
Add some documentation and comments
Signed-off-by: mvglasow <michael -at- vonglasow.com>
|
| |
| |
| |
| | |
Signed-off-by: mvglasow <michael -at- vonglasow.com>
|
| |
| |
| |
| | |
Signed-off-by: mvglasow <michael -at- vonglasow.com>
|
| |
| |
| |
| | |
Signed-off-by: mvglasow <michael -at- vonglasow.com>
|
| |
| |
| |
| | |
Signed-off-by: mvglasow <michael -at- vonglasow.com>
|
| |
| |
| |
| | |
Signed-off-by: mvglasow <michael -at- vonglasow.com>
|
|/ |
|
|
|
|
|
|
| |
During search, clear the list of possible keys when the search input
changes. Otherwise too many keys are highlighted if search input is
changed while the search is still running.
|
| |
|
| |
|
|
|
|
|
|
| |
Simplify gui_internal_keynav_find_prev, and fix small bug:
In the search menu, if the Prev/Next buttons are visible and the
keyboard is hidden, going backwards with PgUp skips some widgets.
|
|
|
|
|
|
|
| |
Allow navigating the menus of the internal GUI with only PgUp/PgDown
keys, instead of using arrow and Enter keys (which remains supported).
This allows to operate the menus with a rotary encoder, if its two
actions are mapped to PgUp/PgDown.
|
|
|
|
|
|
|
|
|
| |
Prevent the Prev/Next buttons in the search dialog from being reachable
using the cursor keys even if they are not displayed.
To reproduce: Open search dialog, press Cursor down until focus returns
to the top of the screen. Without this fix, the Prev button appears at
the top of the screen and is focused.
|
|
|
|
|
|
|
|
| |
Fixes for the on-screen keyboard of the search dialog in the internal
GUI:
Switch the keyboard to lower-case after first input character, even if
entered via the physical keyboard.
Switch back to upper-case and un-highlight all keys if user clears search input.
|
|
|
|
|
|
|
| |
The Prev/Next buttons in the search result list of the internal GUI
can be selected by moving the input focus using the arrow keys. This fix
prevents the Prev/Next buttons from staying hightlighted when the focus
is moved away.
|
|
|
|
|
|
|
|
| |
Do not set locale to "C" for LC_NUMERIC, and do not call setlocale at all on
Android, because:
- Since Lollipop, Android attempts to do something in setlocale, but its
implementation is far from complete and makes no sense for us at this point.
- Older Android versions used to completely ignore setlocale() calls.
|
|
|
| |
Different implementation of #1331 to fix memory leak
|
|
|
|
| |
Signed-off-by: mvglasow <michael -at- vonglasow.com>
|
|
|
|
| |
Signed-off-by: mvglasow <michael -at- vonglasow.com>
|