I meant acceleratedRendering, sorry. I was talking to someone about fullscreenMode right before
I answered you and had a think-o. I do have acceleratedRendering enabled in my app.
I also ran into the problem you described below -- taps went through but the screen did not
redraw so the content d
And it seems that, at least in my last run-in, the taps were actually going
through… it is just that they weren't being drawn on the screen. I had
displayed a group with a visual effect inside a rect… only controls inside the
rect appeared unresponsive. When put away using unlock the screen wit
I don’t use fullscreenMode. Is acceleratedRendering a default requirement of
fullscreenMode?
I’ve been unable to create a simple recipe. In my cases I am suspicious that it
has something to do with overlapping groups… but obviously it is more than that.
—
Scott
> On Jun 1, 2020, at 9:15 PM, J.
On 6/1/20 9:15 PM, J. Landman Gay via use-livecode wrote:
Oh my gosh, I *never* would have guessed that fullscreenMode was the
culprit. That's kind of screwy isn't it? Why would it block taps? And
not consistently either.
WTF?
--
Mark Wieder
ahsoftw...@gmail.com
___
Oh my gosh, I *never* would have guessed that fullscreenMode was the culprit. That's kind of
screwy isn't it? Why would it block taps? And not consistently either.
I'm very glad you knew what was wrong, I was completely at a loss. Thank you. It seems like
this needs a bug report but there's no
For me, when I run across this (and I have several times… including one just
last week) it is almost always acceleratedRendering.
I usually end up toggling it off and on and then all works fine.
Sometimes I wrap code between these but sometimes I just put this at the end of
the handler that in
I’m glad this has been brought up as I have done some internal investigation
myself, with mixed results. A higher education institute I work for pushes us
hard for a11y forward workflows (to the point where we’re supposed to include a
text description of any MEMEs we post in the official Slack
Hi all,
Read about new developments in LiveCode open source and the open source
community in today's edition of the "This Week in LiveCode" newsletter!
Read issue #228 here: https://bit.ly/2Azf3MX
This is a weekly newsletter about LiveCode, focussing on what's been
going on in and around
I am not sure if this will solve your problem, but did you try the touch
messages instead?
Matthias
> Am 01.06.2020 um 21:50 schrieb J. Landman Gay via use-livecode
> :
>
> Has anyone seen this problem? On an iOS build, normal LC controls sometimes
> do not respond to mouseUp events. There
Has anyone seen this problem? On an iOS build, normal LC controls sometimes do not respond to
mouseUp events. There are no native controls involved -- the worst offender is a regular LC
graphic that serves as a login button. Sometimes it just doesn't trigger. Other times it's a
locked LC field t
Yes - just did it. I’m guessing it’s something left over from an earlier
activation of LC, but it’s just a guess. I’ve seen it once before.
Graham
Sent from my iPhone
> On 1 Jun 2020, at 19:01, panagiotis merakos via use-livecode
> wrote:
>
> Hello Graham,
>
> I have not seen that error b
Hello Graham,
I have not seen that error before, but looks like it is coming from the OS.
Did restarting the machine fix the problem?
Kind regards,
Panos
--
On Mon, 1 Jun 2020 at 19:53, Graham Samuel via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Panos, what does “LiveCodeIndy-9_6_0
Panos, what does “LiveCodeIndy-9_6_0-M Resource Busy" mean? Basically I
downloaded the dmg and got that. No other version of LC was open at the time,
but the machine (an iMac running HIgh Sierra) has not been rebooted since the
last use of LiveCode. I will restart now - but it shouldn’t happen,
Dear list members,
We are pleased to announce the release of LiveCode 9.6.0.
Getting the Release
===
You can get the release at https://downloads.livecode.com/livecode/ or via
the automatic updater.
Release Contents
LiveCode 9.6.0 comes with more than 120 chang
14 matches
Mail list logo
