Geometry Manager (was Screen Resolution for Desktop Apps)

Brian Milby brian at
Sun Dec 17 18:14:12 EST 2017

Yes, I’m at fault for the wrong name... sorry about that.

The “remove all” geometry settings button will work properly soon. That
should fix things when they go bad for an individual object. I’m thinking a
command is needed to do the same for an entire card.  (Although
‘revcachegeometry true’ may fix some issues where changes are made in the
PI but not properly updated for the object.)

There are a couple of other things that will be addressed soon too (changes
already merged into 8 or 9 branch).

One thing I notice from the code is that it probably needs to do things in
2 passes instead of one. Order is set by “distance” to an absolute on all
sides. I’m thinking it may be better to do the horizontal separate from the
vertical.  More of an intuition at this point, but one thing I’d like to

I would like to volunteer to work on improving the GM.  I think it would be
a good asset for new users to allow them to concentrate on other things
initially besides resize handlers.

The profile manager also needs to be improved (or at least made easier to
use).  There are a whole different set of issues when using GM/PM together.

I also wonder how much difficulty is due to a clear explanation of how the
GM works.  I know because I’ve been tracing the code, but a new user (or
even most long time users) isn’t going to do that.

So, what should I look at first?  I’ve got some time this week.


On Sun, Dec 17, 2017 at 4:13 PM Richmond Mathewson via use-livecode <
use-livecode at> wrote:

> The identity of Richard is not really that interesting.
> What is interesting is why the Geometry Manager is still inclided in the
> when it just isn't up to scratch: it should be either completely rejigged
> or
> dropped.
> Richmond.
> On 17/12/17 11:06 pm, J. Landman Gay via use-livecode wrote:
> > On 12/17/17 2:54 PM, Mark Wieder via use-livecode wrote:
> >> On 12/16/2017 12:06 PM, Brian Milby via use-livecode wrote:
> >>> Richard, can you outline some of the issues you have seen with the
> >>> GM (or
> >>> point to a thread where it was discussed). On the surface it looks
> >>> like a
> >>> good way to handle many types of positioning needs. There were a
> >>> couple of
> >>> oddities in the code that I’ve looked at already.
> >>
> >> Not sure who "Richard" is, but I can say from experience that the GM
> >> works fine until it doesn't, and then all hell breaks loose and it's
> >> impossible to get rid of the GM artifacts to the point where your app
> >> works again. You end up recreating the app from scratch again and
> >> wishing you had never touched the GM. So I don't anymore.
> >>
> >
> > You can remove the cRevGeometry propery set from each control if you
> > don't want to rewrite the stack. But still...
> >
> > I stopped using it too. It sort of works if it's the last thing you
> > do, but if you change the layout you have to start over again.
> >
> _______________________________________________
> use-livecode mailing list
> use-livecode at
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:

More information about the Use-livecode mailing list