Change to the label property in 6.7

[Peter Haworth]

Thanks Paul.  I'm a little concerned about what happens in your mouseUp
handler if I'm understanding it correctly.  If "Test" doesn't exist in the
button, I would have expected the menuHistory to be zero or empty or
something to indicate that the label doesn't exist in the text of the
button.

Also a bit puzzled by the last sentence since setting the label in 6.6
shouldn't change the menuHistory, although maybe that's related to my first
concern.

ANyway, thanks for checking it out.  I think I will download 6.7 to my
Windows box and see if I can get it to run there.


Pete
lcSQL Software <http://www.lcsql.com>
Home of lcStackBrowser <http://www.lcsql.com/lcstackbrowser.html> and
SQLiteAdmin <http://www.lcsql.com/sqliteadmin.html>


On Sat, Mar 29, 2014 at 2:01 PM, Paul Hibbert <paulhibbert at mac.com> wrote:

> Pete,
>
> It looks like this is OK as far as I can see. I just ran a quick test:
>
> 1 x Option Menu (Default settings)
>    Script:
>         on menuPick
>            put the menuHistory of me into fld 3
>         end menuPick
>
> 1 x Button "Test"
>    Script:
>         on mouseDown
>            put the menuHistory of btn 1 into fld 1
>         end mouseDown
>
>         on mouseUp
>            set the label of btn 1 to "Test"
>            put the menuHistory of btn 1 into fld 2
>         end mouseUp
>
> 3 x Field
>
> The result in all 3 fields was the same after pressing the "Test" button,
> whichever option was chosen last using the optionMenu was the reported
> menuHistory.
>
> The result was identical to LC 6.6
>
> HTH
>
> Paul
>
>
> On 2014-03-29, at 12:36 PM, Peter Haworth <pete at lcsql.com> wrote:
>
> > I've been looking into my stacks to see how they will be affected by the
> > change to the way the label property of an option menu works in 6.7.
> >
> > As long as it will still be possible to set the label of an option menu
> to
> > a value that is not in its text, all should be well.
> >
> > Unfortunately, I can't even run 6.7 on my computer (OSX 10.7.4) as it
> dies
> > a silent death before I can even open a stack (QCC bug report entered).
> Can
> > anyone confirm that the above is still possible and, if so, what value
> ends
> > up in the menuHistory?
> >
> > This change also reminds me that I've always wondered why setting the
> > hilitedline of a scrolling list field does not trigger a selectionChanged
> > message.  It seems analogous to setting the menuHistory of an option menu
> > triggering a menuPick message.
> >
> >
> > Pete
> > lcSQL Software <http://www.lcsql.com>
> > Home of lcStackBrowser <http://www.lcsql.com/lcstackbrowser.html> and
> > SQLiteAdmin <http://www.lcsql.com/sqliteadmin.html>
> > _______________________________________________
> > 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
>