I have a drop down search panel with radio buttons and a search field.
the search string field is grouped with the search icon (magnify glass icon)
this small group of two objects has behavior attached. When the user hits the
search icon, the string and readio buttons all form and run a dbase q
It's not set for "everything" only scrolling groups.
How can it be drawing too much? if there is only one scrolling group on the
card and all other cards, stacks etc are closed or not in view, how does having
the layermode set in an unopened stack start to "draw too much"
??
Jonathan Lynch w
It seems like having the layermode set to scrolling for everything forces it to
draw too much stuff. What happens if you only do one at a time?
Mark W would know more. But, I have found one at a time means it only gives
extra power where it is needed.
Sent from my iPhone
> On Sep 29, 2017, at
Jonathan:
The layermode of the scrolling groups is preset to "scrolling"
The question is about the sequence as it relates to visual layer rendering
Open Stack A, turn on acceleratedRendering
Open Stack B, which also turns on its "own" acceleratedRendering
Close Stack A, *after* having open B "o
Hi Swami,
I turn accelerated rendering on and off depending on which group the user opens
up.
Are you setting the layermode of each group as you go?
Sent from my iPhone
> On Sep 29, 2017, at 1:41 PM, Sannyasin Brahmanathaswami via use-livecode
> wrote:
>
> We continue struggle with our app
We continue struggle with our app on Android and between mobile controls being
instantiated or deleted + oddities with acceleratedRendering, + remote bugging
not *really* working, it's a bit of a fishing expedition when everything works
on desktop and iOS.
A complete document on accelerated ren
Surprise, at least this is new news for some of us: assuming the device
supports one or another, all those services are indeed actually available,
whether you check those boxes or not or so I'm told via another grapevine.
ergo: you only want to check them in the SA builder if your app really, r
Oh right. I should have thought of that.
On September 29, 2017 7:20:29 AM Trevor DeVore via use-livecode
wrote:
What I do is type the word “breakpoint” in script only stacks.
Trevor DeVore
ScreenSteps
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software
> > Reported, of course, #20490.
> Fixed, of course, https://github.com/livecode/livecode/pull/6012.
-:))
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferen
@Quentin L.
Hopefully the following citation can help all of us to understand
better what's going on. Especially point (1) relates to our current
discussion:
Posted by Mark Waddingham in a long thread (2015) in the LC Builder
forum, not hard to find. It still describes at about the current state.
On 2017-09-29 16:15, hh via use-livecode wrote:
Reported, of course, #20490.
Fixed, of course, https://github.com/livecode/livecode/pull/6012.
This patch will be back-ported to 8.1.6 as 8.1.6-gm-3 - this will appear
as soon as we can get it built and uploaded - it will appear in the auto
upd
sez hh :
> > > JLG wrote:
> > > The original issue that influenced this one was how to provide a
> > > larger hit zone on an SVG widget.
> > > How would this property work for that?
>
> > Quentin L. wrote:
> > I?m thinking that a single line of code would suffice:
> >
> > set the clickableRegion o
Reported, of course, #20490.
___
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
On Fri, Sep 29, 2017 at 12:11 AM, hh via use-livecode <
use-livecode@lists.runrev.com> wrote:
> MacOS 10.13, LC 6.7.11/ 7.1.4/ 8.1.6/ 9.0.0-dp9
> (here on Mac mini/late 2012 2.5 GHz i5, Intel Grahics HD 4000)
>
> When using the color dialog from the Property Inspector or via
> "answer color", ever
Even when I use breakpoint, I'm having issues with remote debugging, which
is QR...something.
On Fri, Sep 29, 2017 at 8:18 AM, Trevor DeVore via use-livecode <
use-livecode@lists.runrev.com> wrote:
> On Fri, Sep 29, 2017 at 12:56 AM J. Landman Gay via use-livecode <
> use-livecode@lists.runrev.co
On Fri, Sep 29, 2017 at 12:56 AM J. Landman Gay via use-livecode <
use-livecode@lists.runrev.com> wrote:
> On 9/28/17 8:54 PM, Monte Goulding via use-livecode wrote:
> >
> >> On 29 Sep 2017, at 7:13 am, J. Landman Gay via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >>
> >> Thanks. One
Yes. Probably such bugs as the color picker issue are the reason
for not offering the upgrade via the built-in AppStore updater?
Though it is possible to work around: The GraphicConverter upgraded
yesterday, it has a working color picker.
___
use-liveco
Oops :)
Hmm that's strange, my Mac running 10.12.6 does not offer me to upgrade to
10.13 when I "Check for updates".
Anyway, I will upgrade using your link.
So it looks like the color picker issue is something *we* have to address.
Best regards,
Panos
--
On Fri, Sep 29, 2017 at 9:34 AM, hh via
> Panos wrote:
> MacOS 10.13 is still in beta
No. Official version since Sept 25, 2017.
https://www.apple.com/macos/high-sierra/
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
Hi all,
MacOS 10.13 is still in beta, and several other apps have problems with the
system color picker:
https://www.reddit.com/r/MacOS/comments/6mu94y/anyone_else_noticed_that_on_high_sierra_using_the/
https://vimeo.com/234359128
I am not sure if this is something that Apple plans to fix, or so
20 matches
Mail list logo