Re: Segmented Control Bugs?

2018-02-14 Thread Sannyasin Brahmanathaswami via use-livecode
Thanks, but for now I completely removed it and went back to the "old fashioned" way: three buttons in a group side by side…catch the target. Works like a charm for this use case, not quite as perfect native look and feel on devices, but still looks quite good. Side thoughts on native look and

Re: Segmented Control Bugs?

2017-10-07 Thread Brian Milby via use-livecode
I've posted a PR that should address this issue: https://github.com/livecode/livecode/pull/6044 I created a stack with a segmented control with a substack with a segmented control. As you described, the hiliteChanged message was dispatched for both controls upon opening the stack. In my case, I o

Re: Segmented Control Bugs?

2017-10-05 Thread panagiotis merakos via use-livecode
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 wrote: > LC team: Thanks for getting the docs fixed… can we go back on point? > > Bug still

Re: Segmented Control Bugs?

2017-10-05 Thread Sannyasin Brahmanathaswami via use-livecode
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

Re: Segmented Control Bugs?

2017-10-03 Thread Brian Milby via use-livecode
I think Ali is already on it. He found the commit with the removal. On Tue, Oct 3, 2017 at 3:49 PM James At The Hale via use-livecode < use-livecode@lists.runrev.com> wrote: > Pants wrote>, > > Sorry, I should have been more clear. The "hiliteChanged" is a > **message** > > related to the segmente

Re: Segmented Control Bugs?

2017-10-03 Thread James At The Hale via use-livecode
Pants wrote>, > Sorry, I should have been more clear. The "hiliteChanged" is a **message** > related to the segmented control. In your screenshot, you have applied the > "property" filter, thus this message is not shown. Remove the "property" > filter and this message will appear. Actually no. It

Re: Segmented Control Bugs?

2017-10-03 Thread Ali Lloyd via use-livecode
Appears to be here: https://github.com/livecode/livecode/commit/4a25b3be357bcb8c92523d6f8cc4f9ea5d94836e#diff-48360427573246fc3b20d170e09eb8b1 On Tue, Oct 3, 2017 at 9:38 PM Brian Milby wrote: > That’s what I was just looking at. Develop branch impacted, 8.1 & 8.2 are > good. > On Tue, Oct 3, 20

Re: Segmented Control Bugs?

2017-10-03 Thread Brian Milby via use-livecode
That’s what I was just looking at. Develop branch impacted, 8.1 & 8.2 are good. On Tue, Oct 3, 2017 at 3:18 PM Ali Lloyd via use-livecode < use-livecode@lists.runrev.com> wrote: > Oh, looks like the docs for the segmented control have become mangled > somehow... perhaps a mis-merge. > > On Tue, Oc

Re: Segmented Control Bugs?

2017-10-03 Thread Ali Lloyd via use-livecode
Oh, looks like the docs for the segmented control have become mangled somehow... perhaps a mis-merge. On Tue, Oct 3, 2017 at 8:38 PM panagiotis merakos via use-livecode < use-livecode@lists.runrev.com> wrote: > Hi BR, > > Sorry, I should have been more clear. The "hiliteChanged" is a **message**

Re: Segmented Control Bugs?

2017-10-03 Thread panagiotis merakos via use-livecode
Hi BR, Sorry, I should have been more clear. The "hiliteChanged" is a **message** related to the segmented control. In your screenshot, you have applied the "property" filter, thus this message is not shown. Remove the "property" filter and this message will appear. Best, Panos -- On Tue, Oct 3,

Re: Segmented Control Bugs?

2017-10-03 Thread Brian Milby via use-livecode
Look at the description for the widget. Appears there isn’t a separate dictionary entry. On Tue, Oct 3, 2017 at 1:43 PM Sannyasin Brahmanathaswami via use-livecode < use-livecode@lists.runrev.com> wrote: > I may be blind today… been tracing code for three days… > > see all props listed in the API

Re: Segmented Control Bugs?

2017-10-03 Thread Sannyasin Brahmanathaswami via use-livecode
I may be blind today… been tracing code for three days… see all props listed in the API guide https://www.dropbox.com/s/tpo38y5q491w0hr/seg-control-props.jpeg?dl=0 "hiliteChanged" does not appear among them. On 10/3/17, 5:53 AM, "use-livecode on behalf of panagiotis merakos via use-li

Re: Segmented Control Bugs?

2017-10-03 Thread panagiotis merakos via use-livecode
Hi BR, >>>Though obvious in function, "hiliteChanged" is not a documented property of the segmented control It is documented. In the dictionary, select "Segmented Control" in the API dropdown, and you'll see all the properties/messages related to this widget. Best, Panos -- On Tue, Oct 3,

Re: Segmented Control Bugs?

2017-10-03 Thread Sannyasin Brahmanathaswami via use-livecode
Hmm the bug I have is a bit different… appears in both 8 and 9 I "deprecated" the control by moving it to -2000,-2000 and used the "old-fashioned way" of three buttons in group/get the target and go. save… went off for some other work.. came back Then every time the stack opens, the script o

Re: Segmented Control Bugs?

2017-10-03 Thread panagiotis merakos via use-livecode
Hi BR, The main difference between the segmented control between LC 8.x and 9.0 is that: - In LC 8.x you can select **exactly** one segment - In LC 9 this has changed (--> enhanced) and you can select 0 or more segments See the properties "toggleHilites" and "multipleHilites" in LC 9.0 DP-9. No