<Sigh> Have to eat crow. Another function that set the rect of the stack based 
on the objects it contained was the culprit. 

Bob S


> On Mar 10, 2020, at 08:49 , Bob Sneidar via use-livecode 
> <use-livecode@lists.runrev.com> wrote:
> 
> Hi all. Forgive me for dredging up an old issue again, but this really is a 
> bug. 
> 
> When I close a stack I get the loc of the stack and save it in a custom 
> property. When I open the stack I get that property (I checked that it is 
> identical to what I saved it as) then set the loc of the stack to that. It 
> ends up 11 pixels HIGHER than it was when I saved it!! I check the loc of the 
> stack after it opens that's how I know!!!
> 
> If I set the loc of a stack, and what ends up in the property is SOMETHING 
> OTHER THAN WHAT I TOLD IT TO BE, isn't that a bug, Mac Menu Bars 
> notwithstanding???
> 
> Sorry for sounding animated but this really "bugs" me. 
> 
> Bob S


_______________________________________________
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
  • Revisiting old bones Bob Sneidar via use-livecode
    • Re: Revisiting old bones Bob Sneidar via use-livecode

Reply via email to