Bug 23459
> On Nov 20, 2021, at 5:34 AM, Mark Waddingham via use-livecode
> wrote:
>
> Hi Scott - the touch coords being wrong sounds like a bug to me - can you
> file a report (with example stack if possible).
>
> Thanks!
>
> Mark.
___
Will do.
—
Scott
> On Nov 20, 2021, at 5:34 AM, Mark Waddingham via use-livecode
> wrote:
>
> Hi Scott - the touch coords being wrong sounds like a bug to me - can you
> file a report (with example stack if possible).
>
> Thanks!
>
> Mark.
>
> Sent from my iPhone
>
>> On 20 Nov 2021, at
Hi Scott - the touch coords being wrong sounds like a bug to me - can you file
a report (with example stack if possible).
Thanks!
Mark.
Sent from my iPhone
> On 20 Nov 2021, at 12:04, scott--- via use-livecode
> wrote:
>
> Just answering my own question in case anyone searches this later.
Just answering my own question in case anyone searches this later.
This was kind of a forehead slapper when I finally saw it. There was a native
UIScroller over part of the screen. None of the other buttons on the screen
were inside the rectangle of the scroller, so they weren’t effected. The
Jacque, that is pretty much what I’m doing (except that my semi-transparent
screen graphic is separate from the fake dialog group.) I agree that this
approach normally works well. I don’t have as much experience on Android so I
wondered if it had something to do with the platform. Apparently it
I've done several fake dialogs. The trick is to group the dialog with a a
semi-transparent full screen graphic layered behind the dialog group.
Greying the screen is normal behavior on Android and works on iOS too. The
graphic has blocker mouse handlers so clicking it does nothing. That way
Would it be possible to use a send in time approach? If not for real, you
might could try to avoid the loop as a test. I’ll confess I have not seen that
particular issue though.
Sent from my iPad
> On Nov 19, 2021, at 11:49 PM, scott--- via use-livecode
> wrote:
>
> I’m having trouble
Oh for…
I was unclear in the body of my original post. This is only occurring on
Android. Not iOS or in the IDE.
> On Nov 19, 2021, at 8:47 PM, scott--- via use-livecode
> wrote:
>
> I’m having trouble with an app that up until now has just been for iOS. Most
> of the changes have been
I’m having trouble with an app that up until now has just been for iOS. Most of
the changes have been pretty straight forward but I’ve encountered a specific
case where touching a button doesn’t pass the touch message to the button being
tapped… unless I touch significantly below the button (I