Opened 4 years ago

Last modified 8 months ago

#2749 new enhancement

Integrate 'Change mapset' dialog in manager toolbar

Reported by: mwortmann Owned by: grass-dev@…
Priority: normal Milestone: 7.6.2
Component: wxGUI Version: unspecified
Keywords: mapset, toolbars, layer manager Cc:
CPU: Unspecified Platform: Unspecified

Description

Wouldn't the simple (Settings > GRASS working environment > ) Change mapset dialog be a lot more useful in the Layer Manager toolbar? I'm not sure how many people are actually using the dialog, but I'm sure most use the commandline to do this simple change. I always thought typing 'g.mapset xyz' (plus maybe g.mapset -l) or going to the dialog, seems too much for such a simple thing. The simple dropdown without the Ok button would be quick and easy. Plus it could show the current mapset which is somewhat missing in the Layer Manager.

Change History (14)

comment:1 in reply to:  description Changed 4 years ago by annakrat

Replying to mwortmann:

Wouldn't the simple (Settings > GRASS working environment > ) Change mapset dialog be a lot more useful in the Layer Manager toolbar? I'm not sure how many people are actually using the dialog, but I'm sure most use the commandline to do this simple change. I

I use the dialog quite often when I don't remember the mapset names.

always thought typing 'g.mapset xyz' (plus maybe g.mapset -l) or going to the dialog, seems too much for such a simple thing. The simple dropdown without the Ok button would be quick and easy. Plus it could show the current mapset which is somewhat missing in the Layer Manager.

I mostly agree but I am not sure where to put it, there is already a lot of things in the toolbar, so we would have to start a new row of toolbars? Maybe the data catalog tab would be an option?

BTW, on Ubuntu, you can type Alt and then 'Change ...' and launch the dialog in this way, too.

comment:2 Changed 4 years ago by mwortmann

I had a little fiddle and copying the approach from the mapdisplay toolbox, adding the following lines to the LMWorkspaceToolbar init_ method gives you an impression how it would look like:

        # add mapset selector
        self.combo = MapsetSelect(parent = self, id = wx.ID_ANY, size = (150, -1))
        self.comboid = self.AddControl(self.combo)
        self.parent.Bind(wx.EVT_COMBOBOX, self.OnChangeMapset, self.comboid)

I havent found a working way to for the self.OnChangeMapset? method though. Regarding the size, I have two rows and neither of them is filled. Adding the 150px select combo fills out the top row nicely. I'm running the g.gui from a remote machine, so the Ubuntu shortcut doesnt work for me:$

comment:3 Changed 4 years ago by wenzeslaus

Now I see what you mean. These combos in the toolbars mostly work but in general are best avoided, so I wouldn't add another one if not necessary. The Mapset name is in the Map Display window title, although in a cryptic way.

comment:4 Changed 4 years ago by mwortmann

I agree that in the map display toolbox the combo box is a bit awkward, but I think for a potentially long list of mapsets this would be the most convenient way to change them. Putting a mapset changer a bit more prominent into the gui would also help newbies come to terms with the mapset idea and give them an incentive to use them. I know far too many people starting with grass that just dump all their maps into PERMANENT.

Re displaying the current mapset: The Map Display title doesnt update when you actually change the mapset, which makes it more confusing than helpful sometimes. I tweak my commandline prompter in my .grass.bashrc two have a constant reminder of where I am, which also updates. But there is nothing like that in the gui.

comment:5 in reply to:  4 Changed 4 years ago by wenzeslaus

Replying to mwortmann:

Re displaying the current mapset: The Map Display title doesnt update when you actually change the mapset, which makes it more confusing than helpful sometimes.

This is a clear bug or imperfection, please open another report for that. You can add your suggestion of formatting as well, unless you thing that the current one is ok.

comment:6 Changed 4 years ago by neteler

Milestone: 7.1.07.2.0

Milestone renamed

comment:7 Changed 3 years ago by neteler

Milestone: 7.2.07.2.1

Ticket retargeted after milestone closed

comment:8 Changed 3 years ago by martinl

Milestone: 7.2.17.2.2

comment:9 Changed 2 years ago by martinl

Milestone: 7.2.27.4.0

All enhancement tickets should be assigned to 7.4 milestone.

comment:10 Changed 22 months ago by neteler

Milestone: 7.4.07.4.1

Ticket retargeted after milestone closed

comment:11 Changed 17 months ago by neteler

Milestone: 7.4.17.4.2

comment:12 Changed 14 months ago by martinl

Milestone: 7.4.27.6.0

All enhancement tickets should be assigned to 7.6 milestone.

comment:13 Changed 10 months ago by martinl

Milestone: 7.6.07.6.1

Ticket retargeted after milestone closed

comment:14 Changed 8 months ago by martinl

Milestone: 7.6.17.6.2

Ticket retargeted after milestone closed

Note: See TracTickets for help on using tickets.