LiveCode Forums.

When moving objects, if the shift key is down limit movement to same horizontal loc if move horizontal or same loc vertically if move vertical.

@melristau
I think Richard was directing you to see this old "Bug" report from 2008!! (said tongue-in-cheek, Richard)
http://quality.livecode.com/show_bug.cgi?id=7380

I know this posting is a month old, but the same thought was rolling in my head for the last couple weeks. It is a surprise that LC doesn't have this - even Adobe adopted this in Illustrator years ago. In particular, I find using the option/alt keys along with shift makes GUI layouts quick and simple. Why fiddle with piddly arrows "Ctrl C, Ctrl V, click, click, click, a little left, a little right, a little up" when you could quickly and easily "shift-drag, alt/option, drop a copy" - exactly lined up and ready to move on. When in the design flow, it is these little speed bumps that can easily derail the train of creativity.

What is a better method to deal with these kinds of requests. Technically, if a feature doesn't exist, it's not really a bug report. And being a feature request, I don't really want to clog up a Bug report list.

Thinking out loud here, maybe we need to refine the forum channel for Feature requests and community discussions of these requests. If it was broken down into categories: UI requests, OSX/iOS/Win/Android/Server specific requests, data handling, image handling, etc,. would this help to clean up the requests and eliminate potential duplicates? I haven't spent much time on the Feature Request forum, but just adding my $0.02.

Cheers,
MadDogDean

MadDogDean wrote:@melristau
I think Richard was directing you to see this old "Bug" report from 2008!! (said tongue-in-cheek, Richard)
http://quality.livecode.com/show_bug.cgi?id=7380

Not tongue-in-cheek at all. I didn't know about the existing enhancement request - thanks for providing the link to that.

I linked to the bug DB because that's where feature requests go too. When submitting a new report there's a flag tor designating whether it's a bug or an enhancement request. Both need to go into that DB to become actionable. This forum section predates the bug DB being publicly available, and to be honest I'm not sure what to do with it at this point. Its existence misleads people into believing that submitting a request here could become actionable, which isn't the case. But there is some value in having this section as a place to discuss possible enhancements, to work out details before submitting them to the team in the DB. Suggestions on how we might make that clearer here?

With Bill's request already there, it may be helpul to add your own notes to it to provide further guidance. While LiveCode isn't a drawing tool per se, I agree that its visual layout capabilities suggest this sort of thing could be useful. Some projects may rely on existing behavior, though, so it may be best if this were governed by a global property so it could be toggled on and off. It may be helpful to suggest a name for that new global property when adding to that request. Naming things is one of the hardest aspects of programming.