Change in behavior of minHeight property

[dunbarx at aol.com]

I would say it is not a bug, but rather a feature. For example, if you lock the position and size of an object in the inspector, the resize handles gray out, and to all intents, the thing seems set in stone. But the arrowKeys will move it (I find this dodge useful), and of course any script may have its way with it, all while still "locked". 


This sort of locking is to keep users and their precocious mice at bay, not the authors.


Craig



-----Original Message-----
From: Peter Haworth <pete at lcsql.com>
To: How to use LiveCode <use-livecode at lists.runrev.com>
Sent: Fri, Jan 3, 2014 6:55 pm
Subject: Re: Change in behavior of minHeight property


I found the same change between 5.5.4 and 6.5.1.

Hard to say if this this is a bug in the software.  However, IMHO, it's a
serious bug in the release notes for 6.5.x.  Changes in legacy behavior
whether as the result of a bug fix or a whim on someone's part should be
very clearly and unmistakenly documented in the release notes.

Pete
lcSQL Software <http://www.lcsql.com>


On Fri, Jan 3, 2014 at 2:58 PM, Devin Asay <devin_asay at byu.edu> wrote:

> In all versions of LC and Rev prior to 6.5, setting the minHeight of a
> stack, when the stack's height was smaller than the new minHeight, resulted
> in the stack being resized to the new minHeight. This behavior changed in
> 6.5. Now setting the minHeight/Width of a stack has no effect on the size
> of the stack. This bit me recently in a sample stack that I send out with
> LiveCode University, which resizes itself when the user clicks a button.
> (The same thing happens with the minWidth, BTW.)
>
> I went to the Dictionary to read up on this behavior, and it seems that
> the minHeight, as documented, is only supposed to restrict the ability of
> the user to resize below the set value. It does not restrict the ability to
> set the dimensions of the stack via scripting.
>
> So the question: is this change in behavior a bug? The new behavior seems
> more in line with the documentation, still, it broke my older stack. I'll
> create a bug report if others think it's warranted.
>
> Can others verify?
>
> Regards,
>
> Devin
>
>
> Devin Asay
> Learn to code with LiveCode University
> http://university.livecode.com
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
_______________________________________________
use-livecode mailing list
use-livecode at lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode