Ditto. The GM seems like a good idea when you first start poking around
with it, and as long as you're doing simple things with it it all seems
dandy. But sooner or later you'll come across something you need to do,
some object that has to be positioned relative to something else, that's
just difficult to do in the GM. And by the time you figure it out and
go through all the clicking, how much time was saved?
Writing your own resizeStack handlers is very liberating. Sure, it can
be a bit tedious, but you generally only need to do it once and forget
about it until you make serious changes - when you'd have to redo all
your GM clicking anyway.
With your own custom code you have complete control over everything.
Well worth the modest effort.
--
Richard Gaskin
Fourth World Systems
Software Design and Development for the Desktop, Mobile, and the Web
____________________________________________________________________
ambassa...@fourthworld.com http://www.FourthWorld.com
Roger Eller wrote:
My advice is don't use it on any complex layout. Also, it only works for
desktop. Mobile has a couple of other options for resolution independent
scaling. The general consensus is to code your own unless the layout is
super simple.
On Sep 17, 2015 6:06 PM, "Rick Harrison" <harrison at all-auctions.com> wrote:
Any advice?
> On Sep 17, 2015, at 9:15 AM, Rick Harrison <harrison at all-auctions.com>
wrote:
>
> Hi there,
>
> I was wondering what the status of the Geometry Manager is currently.
> Does it work as expected, or is it broken?
>
> Do any of you use it? Is it worth trying to make it work, or should I
> just write my own routines to handle stack resizing situations?
>
> Thanks,
>
> Rick
>
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
