New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UI: current active tab is not remembered during session? #53
Comments
Another thing... are most users not used to using LonLat/XY so NOT the Google YX version which is now the default when you install the plugin? |
Ah, wait, it is more subtle: if you use (of course) the little 'wrench' icon in the Zoom to Coordinate panel, then you open on Zoom to tab. But... that is the easiest way to open the Settings.... |
@rduivenvoorde I am also fine with adding the settings button to the main toolbar. I have contemplated doing that in the past and it can be easily done. The settings button on the zoom to and multi-zoom to tools were specifically designed to go to their appropriate settings tab. BTW do you have any idea on how to solve issue #52 ? |
Richard, I am going to keep the default YX, lat/lon order, but I have added the settings icon to the toolbar. I also realized that I was using two different settings icons and made them all the same. Clicking the Settings icon from the toolbar will remember which tab you were last on. I have released Lat Lon Tools 3.4.5 with this change. |
@hamiltoncj Thanks! Fine with me, I already put it in my handouts: "DO NOT forget to change coord order" :-) |
During writing a little handout and writing about using the settings for latlon tools, it appeared to me that it does not remember the latest used tab in the settings, it always opens on 'Zoom to'.
If I just changed something in the Capture tab, and after testing want to change it back, I see that users then are editing the 'Zoom to' settings, because that is what is shown then... And though different it is for non geo-peeps all abacadabra anyway, so they do not see the difference sometimes.
I think this is a simple fix. If I have time I can probably do it myself :-)
The text was updated successfully, but these errors were encountered: