Feature request: Add "hide and show" checkboxes for routes and tracks

Issue #246 wontfix
Christoph Rottleb
created an issue

Dear developers,

when editing routes and tracks, their next generations may lie one over the other, when working with clones of existing routes and tracks.

If you don't want to get confused, you have to save new tracks in new projects. This may result in clutter on the workspace and in the file system.

It could enhance clarity, if it was possible to hide routes and tracks that bother; and show routes and tracks, that are of in the focus of interest by ticking a checkbox.

Up to now, it is possible to hide / show whole projects by ticking a checkbox. The same feature should also be available for routes and tracks.

Please have a look at the attached picture; one look will make it clear, what I am trying to describe in words. It is a modification of a screenshot out of Qmapshack.

With honest regards,

Christoph Rottleb from Kiel, Germany

Comments (4)

  1. kiozen

    This has been suggested a few times by now, but I still don't like the idea to spam the workspace with checkboxes. Especially not as it turns the workspace into something that is provided by the database already. The workspace is not a place to dump all of your data. That is what the database is good for. Keep in mind that all data on the workspace has to be handled by the render engine of QMapShack. That is why I encourage everyone to load only the data needed for the current task.

    Open a project folder for planning in the database. Place all data you need in this folder. Use the checkboxes to load the parts you need for the current task into the workspace. Uncheck what ever you do not need.

    Your workspace is like your desk. If you pile all your stuff on the desk it's getting hard to work. Even if you have a decent system to keep some kind of order. If you put all stuff into the folders of your drawer and only fetch those things you work with it's much easier.

  2. Christoph Rottleb reporter

    In the meantime I was working on some hiking tours, but I still can't warm to your approach.

    My workflow is like that:

    (A) I load a recorded track for optimization or modification. It often contains loops (deviations, going back and return) that I want to cut off or parts, I want to replace by better directions. When I cut the track, this results in new tracks: one or two tracks I want to keep, and one or two tracks I want to delete. Before deleting the unwanted tracks I would like to use "hide /show" the respective object to preview the result.

    (B) I make up a route and transform it into a track. Then I would like to hide the route, so that it doesn't bother while editing the resulting track (doing split and merge). Else I would like to keep the original route for trying new variants later.

    By now, you have to put each and every track or route in a separate project to be able to show / hide it.

    Else for data safety reasons. Now I have to save each and every track or route into a separate file. That causes clutter in the file management.

    This is probably the reason, why a .gpx file can hold more than one track/route to avoid the need of storage in different files.

    On the workspace it looks for me the same, if I load several "one item projects" in the database or one project with several items. I would prefer keeping all items, that belong together, in one project. It should be up to the user, not to overload a project.

    With best regards,

    Christoph Rottleb from Kiel, Germany

  3. kiozen
    • Create a database
    • Create a project in the database
    • Check the project. It will be loaded into the workspace.
    • Create what ever items you want in the project on the workspace. Or copy items from other projects.
    • Use CTRL+S frequently to save everything into the database.
    • Use the checkboxes in the database to load/remove objects.
    • Delete items in the database.

    You see only one project. No clutter. 100% control on what to see on the workspace.

  4. Log in to comment