Comment 10 for bug 927898
Revision history for this message
| Diederik van Lierop (mail-diedenrezi) wrote Re: [Bug 927898] Re: snap to guides no longer working for path nodes or rotation origin | #10 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0f7b58d
(Get the code!)
On 02/20/2012 03:40 PM, LucaDC wrote:
> >What happens to the global toggles if one of the granular toggles is changed?
> I thought them to be completely independent: the global simply turns all off or enables those that are set. This doesn't prevent you changing the granular ones when the global is off (simply nothing will change until you turn it on).
That would be the most straightforward solution, but if for example one
button on the toolbar affects 2 independent toggles, then what do we do
with the status of the button after one of the 2 toggles has changed?
> >We currently have 23 different snap sources, and 38 different snap targets. Should we expose all of them?
> Gulp. This means 23*38=874 possible interactions to manage.
IMHO we should only consider to give each of the 23 sources an
individual toggle, and each of the 38 targets. Then, if you really want
to snap exclusively a gradient handle to a circle center, then only one
toggle in each of the source and target groups should be enabled.
Allowing to set each combination individually would be really too much.
> Why not saving a single string as binary values (like when you embed a picture)? Is that allowed by SVG? Many bits, few characters.
Yes, that's the way to go.