Switching Grid "#" should also represented in the GUI Button, same for Guides

Bug #1517811 reported by Anonymous
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
Expired
Undecided
Unassigned

Bug Description

a more minor feedback:
If Grid is enabled, and also snapping to grid is enabled too in the GUI, then the snap to grid button is active. If I now disable the grid by pressing the "#"-key, grid and snap to grid is off, but the GUI Button for snap to grid is still activated. Same behavior with guides.
In my opinion, the GUI buttons should be synchronized with the actual state.

Anonymous (susi-8888)
summary: Switching Grid "#" should also represented in the GUI Button, same for
- Guidesdisable
+ Guides
Revision history for this message
su_v (suv-lp) wrote :

Please add information about OS/platform and Inkscape version to the bug description, thank you.

Could you please clarify - do you mean the button on the snap controls bar, or the checked status of the menu item (bug #1136344)?

If this proposal is about tying (some of) the current document's snap settings to a view mode (for grids, and/or guides): What is the rationale behind introducing limitations for all users as to when they are allowed to configure (some of) the document's snap settings (i.e. to toggle on/off certain snap sources/targets)?

tags: added: grids guides snapping ui
Changed in inkscape:
status: New → Incomplete
Revision history for this message
Diederik van Lierop (mail-diedenrezi) wrote :

If a document has no objects with smooth nodes, should we then also disable the button for snapping to smooth nodes? And if it has no text objects, then also disable the button for snapping to text objects?

Revision history for this message
Anonymous (susi-8888) wrote :

please apologize:
Version: InkScape 0.91 r13725 (64 bit) and OS Windows 7 prof, 8 GB RAM

I meant the button(s) in the snap control bar.

My thinking behind this proposal was: If a certain snapping is disabled, then (to my opinion) it would be helpful, if this status is also shown in the related button of the snap control bar. This may have even more consequences: if a user is first disabling the grid or guides in the view menu (which implicitly disables the snapping to these no longer active visible things) , and the snap control button is following (shows inactive state), and in a second action the user is enabling the lets say grid snapping again in the snap control bar, that these action then also needs to enable the grid view again...?
Like pulling a new guide into a document with disable guide view enables the guide view implicitly.

my comment to #2: If doing so, then I would report a click to such a document content based disabled button with a message like "inactive option, no text items available in actual document"

Revision history for this message
Anonymous (susi-8888) wrote :

One more comment: I don't like to limitate users here, my thinking is only to be consistent with InkScapes behavior. Disabling the grid view not necessarily means, that you must or should disable the snap to grid. I am aware of Software, where these two items are independent. Means, you could snap to grid even if the grid is invisible. In this case, my expectation would be, that we may have four options (states):
a) Grid visible, no snap (currently implemented)
b) Grid visible, snap to grid active (currently implemented)
c) Grid invisible, no snap (currently implemented) -> that was my observation
d) Grid invisible, snap to grid active (currently not implemented)

Revision history for this message
LucaDC (lucadc) wrote :

The "snap to grid" button in the snap bar is not an indication that snapping to the grid must happen, it's just a request the user makes that "as soon as it's the case, please snap (also) to the grid".
Of course if there's no grid, just as all other types of snapping targets, there will be no snapping. No need to disable the buttons and annoy the user with pedantic warnings.
Or we could disable the eraser tool for blank documents and tell the user that tries to select it: "Please draw something before attempting to erase it!" :)

The implementation of snapping to an inactive grid is an independent feature that should be tied to the grid, not to the button. Imagine you have more than one grid: how can you select to which of them you want to snap to? Always to all? You have to move the enable/disable option per grid.
My personal opinion is that the simplest solution is the current one: you snap to the grids you see.

Revision history for this message
LucaDC (lucadc) wrote :

My fault I didn't check before writing: the option to snap to an invisible grid is already implemented in the grid dialog (option d in comment #4).

Revision history for this message
Anonymous (susi-8888) wrote :

agree to statement #6, please apologize that I overlooked it
seem I am bothering you in #5, I definitely don't want to overload Inkscape with useless messages....

Due to #6, my request even make no sense any longer.

On my system with a file having two grids defined, there still seems to be on inconsistency:
first grid: name = grid0p2mm, "Enable" = unchecked, but the check boxes for "Visible" and "Snap to visible grid lines only" are checked, but greyed out (inactive)
second grid: name=grid1p0mm, "Enable" = checked, "Visible" = checked and "Snap to visible grid lines only" not checked.

Grid View disabled from the Menu, "Snap to Grid Button" from the snap control bar enabled.
(So no grid visible, but it should snap to the "grid1p0mm"?)
I could not snap a drawing element (rectangle) to the in-visible grid.
I also deleted the second grid, and was still unable to snap to the invisible grid.
I attached a screen dump from the GUI and the svg-file with one grid definition left.

OK, I found, It only snaps to the invisible grid, if the grid is enabled in the menu, and both the "Visible" and "Snap to visible grid lines only" check boxes are unchecked in the Grid Tab (see attached screen dump)

Anyhow, I am join you opinion, only snapping to visible things is for me the most common use case too.
And at least, thanks for your contribution for this excellent piece of software!

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Inkscape because there has been no activity for 60 days.]

Changed in inkscape:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.