Segmented Control Bugs?

[panagiotis merakos]

Hi Brahmanathaswami,

What you see is a bug, see this report:

http://quality.livecode.com/show_bug.cgi?id=20509

Best,
Panos
--

On Thu, Oct 5, 2017 at 9:45 PM, Sannyasin Brahmanathaswami via use-livecode
<use-livecode at lists.runrev.com> wrote:

> LC team: Thanks for getting the docs fixed… can we go back on point?
>
> Bug still stands
>
> The segmented still seems to be "globally enabled" and "hears" the
> hilitedChanged msg from "across the universe"
>
> -- when card is opened even though no handler is checking that property
> -- even from a top stack A when the stack with the segmentedcontrol is a
> substack B which is still open "behind"
> -- clicking on a widget on the top stack A (with hilited checked) .. the
> segmentedControl in substack B  which has a script like this
>
> on hiliteChanged
>    put the hilitedItemNames of me into tName
>    put tName into sPreviousSelection
>    answer tName with "OK"
>     #DoSomething
> end hiliteChanged
>
> fires.. and you get the answer dialog.
>
> I just wanted to see if that was an oddity I had created or if this is
> what you see also. (anybody)
>
>
> On 10/3/17, 10:18 AM, "use-livecode on behalf of Ali Lloyd via
> use-livecode" <use-livecode-bounces at lists.runrev.com on behalf of
> use-livecode at lists.runrev.com> wrote:
>
>     Oh, looks like the docs for the segmented control have become mangled
>     somehow... perhaps a mis-merge.
>
> _______________________________________________
> 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
>