On Mon, May 28, 2012 at 3:12 PM, Bryan Hoyt | Brush Technology <bryan@...2310...> wrote:
Please no. Reading the bug report, the entire issue seems to be based on the assumption that toggling guide visibility when there are no guides is confusing to the poor, easily befuddled users. This, of course, is a false assumption ;)
I can certainly understand this assumption. I get confused by features that appear to do nothing when I enable them. "Does that actually work, or is this a bug? [...]
Ah - but toggling guides when there are none *does* do something. It shows you that there are actually _no guides_ ;) I would consider any other behavior a bug.
IMO this is not a problem at all, or else one that could be solved by GATFM (Glancing At The Fine Manual). When creating a new document the first thing you *could* do is turn off visibility on the base layer. You likely shouldn't do that -- it would be silly -- and yet, you are free to do so.
Using a graphics program to its fullest requires knowledge and some research. That being said, features should be as easy to discover as possible. Which is why I'm all for toggling the menu command between 'Hide Guides/Show Guides' [1], but 1000 times against hiding the action deep on some tab in the document properties. And at almost no point will I want or need guides round the edge of the page. That's what the page boundaries are for ;)
Chris
[1] is this even feasible? I know next to nothing about how the menus are created. Can they be updated on the fly?