This object is in archive! 
New screen for "Points" - order of tabs
Completed
In next Locus version will be introduced new screen for Points.
For common points will have two tabs: Basic, Attachments
For geocachas will contain tabs: Basic, Attachments, Listing, Images, Waypoints, Logs,
Where:
Basic - main tab will all possible information about point, location, geocache parameters etc.
Attachments - tab that handle all point attachments
Listing - long listing of cache (visible only if listing exists)
Images - tab created for "Offlinized cache"
Waypoints - new tab for work with cache waypoints
Logs - tab that contain all stored logs for cache
I would like to open discussion and voting for order of these tabs
Order of tabs in new screen for "Points"
-
13%
-
7%
-
18%
-
11%
-
40%
-
4%
-
2%
Because number of votes show, that you really want an ability to define order
since version 2.20.2, Locus will offer configuration of tabs order over 'config.cfg' file
In file will be this new parameter
# Order of tabs in 'Point screen'. Define it as a list of ID's separated by '|'
# options: basic - 1, attachments - 2
# geocaching: listing - 11, images - 12, spoilers - 13, logs - 14, trackables - 15, waypoints - 16
gui_point_screen_tabs_order=
By default, parameter will be empty. You may define list of tabs like this
gui_point_screen_tabs_order=2|16|1|14
Also
you do not have to define all tabs, just those you want to have at
start. Locus automatically add remaining tabs to the end.
Because number of votes show, that you really want an ability to define order
since version 2.20.2, Locus will offer configuration of tabs order over 'config.cfg' file
In file will be this new parameter
# Order of tabs in 'Point screen'. Define it as a list of ID's separated by '|'
# options: basic - 1, attachments - 2
# geocaching: listing - 11, images - 12, spoilers - 13, logs - 14, trackables - 15, waypoints - 16
gui_point_screen_tabs_order=
By default, parameter will be empty. You may define list of tabs like this
gui_point_screen_tabs_order=2|16|1|14
Also
you do not have to define all tabs, just those you want to have at
start. Locus automatically add remaining tabs to the end.
Attachments, Waypoints, Basic, Listing, Logs, Images OR configurable. :-)
Attachments, Waypoints, Basic, Listing, Logs, Images OR configurable. :-)
Voted for possibility Basic, ... Attachments. It seems to be a logical solution for me in the order of importance.
Voted for possibility Basic, ... Attachments. It seems to be a logical solution for me in the order of importance.
I suppose that the active (default) tab would be still "Basic", right? Or the first one?
I suppose that the active (default) tab would be still "Basic", right? Or the first one?
I also think "Basic" have to be the default tab.
I also think "Basic" have to be the default tab.
Voted "Basic ... Attachments" for common points.
I think 'config.cfg' is useful for geocache points.
Voted "Basic ... Attachments" for common points.
I think 'config.cfg' is useful for geocache points.
It doesn't matter but make it configurable over 'config.cfg' file
thanks for poll
It doesn't matter but make it configurable over 'config.cfg' file
thanks for poll
Voted "Basic ... Attachments" but configurable via config.cfg is acceptable too.
Voted "Basic ... Attachments" but configurable via config.cfg is acceptable too.
configurable is always fine ;-) but basic should be the "start"-screen, than it will be also good to scroll to left for waypoints (like in C:geo) ;-)
configurable is always fine ;-) but basic should be the "start"-screen, than it will be also good to scroll to left for waypoints (like in C:geo) ;-)
I also agree. For this is there untouched five option ;)
I also agree. For this is there untouched five option ;)
Voted Basic ...... Attachments. Agree with KaHeMu it is the logical solution and in in order of importance for me. Also, as it does in the test version, when guiding to a point remember last tab viewed when reopened.
Voted Basic ...... Attachments. Agree with KaHeMu it is the logical solution and in in order of importance for me. Also, as it does in the test version, when guiding to a point remember last tab viewed when reopened.
I've hit basic....attachments. But if one can configure (reorder) it as he wants, then it does not matter :)
I've hit basic....attachments. But if one can configure (reorder) it as he wants, then it does not matter :)
configurable is best way ;-) basic should be the default and then scroll to left/right on configurable tabls
configurable is best way ;-) basic should be the default and then scroll to left/right on configurable tabls
I would like to reorder my tabs. Is there any section in configuration file?
I would like to reorder my tabs. Is there any section in configuration file?
Not yet. I'm still collecting votes to see if this configuration is really needed ...
Not yet. I'm still collecting votes to see if this configuration is really needed ...
Waypoints tab is often empty and it would be better to shift this tab to first left tab position. But "start tab" (first tab which appears after point tapping) should be 'Basic'.
As I know 'start tab' can be set in a config file.
Waypoints tab is often empty and it would be better to shift this tab to first left tab position. But "start tab" (first tab which appears after point tapping) should be 'Basic'.
As I know 'start tab' can be set in a config file.
I also think so, but as you may see, this last option has no votes
I also think so, but as you may see, this last option has no votes
But the second option is very similar and I voted for it. It's a pity that the voting is "radius" and not "checkbox". :)
But the second option is very similar and I voted for it. It's a pity that the voting is "radius" and not "checkbox". :)
Basic, Listing, Waypoints, Logs, Attachments, Images
Basic, Listing, Waypoints, Logs, Attachments, Images
Because number of votes show, that you really want an ability to define order
since version 2.20.2, Locus will offer configuration of tabs order over 'config.cfg' file
In file will be this new parameter
# Order of tabs in 'Point screen'. Define it as a list of ID's separated by '|'
# options: basic - 1, attachments - 2
# geocaching: listing - 11, images - 12, spoilers - 13, logs - 14, trackables - 15, waypoints - 16
gui_point_screen_tabs_order=
By default, parameter will be empty. You may define list of tabs like this
gui_point_screen_tabs_order=2|16|1|14
Also
you do not have to define all tabs, just those you want to have at
start. Locus automatically add remaining tabs to the end.
Because number of votes show, that you really want an ability to define order
since version 2.20.2, Locus will offer configuration of tabs order over 'config.cfg' file
In file will be this new parameter
# Order of tabs in 'Point screen'. Define it as a list of ID's separated by '|'
# options: basic - 1, attachments - 2
# geocaching: listing - 11, images - 12, spoilers - 13, logs - 14, trackables - 15, waypoints - 16
gui_point_screen_tabs_order=
By default, parameter will be empty. You may define list of tabs like this
gui_point_screen_tabs_order=2|16|1|14
Also
you do not have to define all tabs, just those you want to have at
start. Locus automatically add remaining tabs to the end.
Thanks for insert this config option ;-) i am happy
since´version 2.20.2
do you mean the next official release ??
I didnt find it in V2.20.2 testversion
Thanks for insert this config option ;-) i am happy
since´version 2.20.2
do you mean the next official release ??
I didnt find it in V2.20.2 testversion
you already have 2.20.2 version? If you mean test version, latest is 2.20.0.2 :)
Test
versions are numbered as four numbers, major official as X.1.0, X.2.0,
minor versions as X.X.1, X.X.2. So yes, i next minor version or today
afternoon in next test version
you already have 2.20.2 version? If you mean test version, latest is 2.20.0.2 :)
Test
versions are numbered as four numbers, major official as X.1.0, X.2.0,
minor versions as X.X.1, X.X.2. So yes, i next minor version or today
afternoon in next test version
sorry and thanks for opening my eyes
sorry and thanks for opening my eyes
no need to sorry :). It's just my way how I create numbers for versions
no need to sorry :). It's just my way how I create numbers for versions
Replies have been locked on this page!