Re: Weird behavior for modal stacks and answer dialogs

2019-09-10 Thread Giovanni via use-livecode 
Hi Mark,
thank you for highlighting the 14275 report.
I can confirm the Spotify “interference” on Yosemite and Sierra. It seems to be 
ininfluent on latest version like Mojave.
I want to underline that this wrong behavior is present also in the 
executables, that is the real problem.

Is there a way to understand what’s going on with 3rd part software?


> Il giorno 09/set/2019, alle ore 17:44, Mark Waddingham via use-livecode 
>  ha scritto:
> 
> On 2019-09-09 16:16, Giovanni via use-livecode wrote:
>> Hi everybody,
>> thanks for feedback.
>> I think that the ones suggested cannot be considered as a solutions
>> nor a workarounds.
>> If I am working on an application with thousands (literally) of
>> answer/ask dialogs and modal called windows I cannot review all my
>> code to find a way to do something that the engine is called to do on
>> its own, don’t you think?
>> Anyway the “lock messages” can be used with answer/ask dialog but not
>> with modal windows that are intended to be used by the user.
>> Moreover as the modal stack behavior is correct on Windows and seems
>> to be correct on latest MacOS versions I found really strange to
>> garbage my code to workaround an issue that, in my opinion, can be
>> classified as a bug.
> 
> This sounds like  > - the
> bug appears to be triggered when certain other apps are running but we have
> yet to be able to find out *why* these other apps have an effect on LC :(
> 
>> During my investigation I found an interesting thing: starting
>> QuickTime to produce a screencast the app starts working properly even
>> without closing/restarting it. Closing QuickTime immediately
>> reintroduce the problem. This sounds like QuickTime uses a system
>> library that LC should use but doesn’t. Can someone give an hint about
>> this?!
> 
> That is intriguing - the fact that QT makes LC's modal windows work correctly
> again is potentially quite a useful discovery. Do the machines which exhibit
> the bug have any 'always running' software (e.g. like Spotify as suggested
> in the above bug).
> 
> Warmest Regards,
> 
> Mark.
> 
> -- 
> Mark Waddingham ~ m...@livecode.com  ~ 
> http://www.livecode.com/ 
> LiveCode: Everyone can create apps
> 
> ___
> 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 
> 
___
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

Re: Weird behavior for modal stacks and answer dialogs

2019-09-09 Thread Mark Waddingham via use-livecode 

On 2019-09-09 16:16, Giovanni via use-livecode wrote:

Hi everybody,
thanks for feedback.
I think that the ones suggested cannot be considered as a solutions
nor a workarounds.
If I am working on an application with thousands (literally) of
answer/ask dialogs and modal called windows I cannot review all my
code to find a way to do something that the engine is called to do on
its own, don’t you think?
Anyway the “lock messages” can be used with answer/ask dialog but not
with modal windows that are intended to be used by the user.
Moreover as the modal stack behavior is correct on Windows and seems
to be correct on latest MacOS versions I found really strange to
garbage my code to workaround an issue that, in my opinion, can be
classified as a bug.


This sounds like  - 
the
bug appears to be triggered when certain other apps are running but we 
have
yet to be able to find out *why* these other apps have an effect on LC 
:(



During my investigation I found an interesting thing: starting
QuickTime to produce a screencast the app starts working properly even
without closing/restarting it. Closing QuickTime immediately
reintroduce the problem. This sounds like QuickTime uses a system
library that LC should use but doesn’t. Can someone give an hint about
this?!


That is intriguing - the fact that QT makes LC's modal windows work 
correctly
again is potentially quite a useful discovery. Do the machines which 
exhibit
the bug have any 'always running' software (e.g. like Spotify as 
suggested

in the above bug).

Warmest Regards,

Mark.

--
Mark Waddingham ~ m...@livecode.com ~ http://www.livecode.com/
LiveCode: Everyone can create apps

___
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

Re: Weird behavior for modal stacks and answer dialogs

2019-09-09 Thread Giovanni via use-livecode 
Hi everybody, 
thanks for feedback.
I think that the ones suggested cannot be considered as a solutions nor a 
workarounds.
If I am working on an application with thousands (literally) of answer/ask 
dialogs and modal called windows I cannot review all my code to find a way to 
do something that the engine is called to do on its own, don’t you think?
Anyway the “lock messages” can be used with answer/ask dialog but not with 
modal windows that are intended to be used by the user.
Moreover as the modal stack behavior is correct on Windows and seems to be 
correct on latest MacOS versions I found really strange to garbage my code to 
workaround an issue that, in my opinion, can be classified as a bug.

During my investigation I found an interesting thing: starting QuickTime to 
produce a screencast the app starts working properly even without 
closing/restarting it. Closing QuickTime immediately reintroduce the problem. 
This sounds like QuickTime uses a system library that LC should use but 
doesn’t. Can someone give an hint about this?!


> Il giorno 09/set/2019, alle ore 13:30, Paul Dupuis via use-livecode 
>  ha scritto:
> 
> On 9/9/2019 6:50 AM, Giovanni via use-livecode wrote:
>> Hi everybody,
>> I’m writing here to report a very strange behavior of modal stacks and 
>> answer dialogs on MacOS Yosemite and Sierra.
>> Basically the modal windows or dialogs, in these OSes simply does not work 
>> and this seems to happen since LC 6.7.x!
>> When you open a modal stack the expected behavior is that the script 
>> execution is interrupted and you cannot interact with the calling or other 
>> opened windows. While the first thing seems to happen, the second one 
>> doesn’t work: you can click on buttons, fields or any other control in the 
>> calling stack or any other stack opened.
>> I think that this is a very big problem mainly in porting applications from 
>> older versions of LC to the newest one and it’s quite strange that nobody 
>> else noticed this before or consider this a problem.
>> 
>> I already filed a bug report at 
>> https://quality.livecode.com/show_bug.cgi?id=22368 
>>  in which you can also 
>> find a demo stack to easily reproduce the behavior.
>> 
>> Anyone can comment on this? Are you experiencing this as a problem? Is there 
>> a workaround or a solution for this?
>> 
>> The problem seems not to be present on Mojave but I was not able to try on 
>> other versions on MacOS and it’s not present on Windows.
>> 
>> 
> 
> This one has been around for a while, and I thought it had been previously 
> reports (but still not fixed). I seem to recall there was a lengthy 
> discussion of it on the list a long time ago.
> 
> The work-around seems to be locking things down before calling an ask or 
> answer dialog (lock messages, lock your menus and so on) so that no other 
> user actions can start any other script.
> 
> ___
> 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


___
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

Re: Weird behavior for modal stacks and answer dialogs

2019-09-09 Thread Bob Sneidar via use-livecode 
In more recent versions of MacOS the ability to interact with an application 
that was not the foreground application was added as a feature. For instance I 
can scroll a web page using the mouse wheel even though the web browser is not 
the frontmost app. I'm not sure how this could be disabled for modal windows 
only. 

I have seen other apps that do NOT allow interaction with a window if it is in 
the background. Perhaps what we need is a new command to turn off background 
interaction?

Bob S


> On Sep 9, 2019, at 04:30 , Paul Dupuis via use-livecode 
>  wrote:
> 
> On 9/9/2019 6:50 AM, Giovanni via use-livecode wrote:
>> Hi everybody,
>> I’m writing here to report a very strange behavior of modal stacks and 
>> answer dialogs on MacOS Yosemite and Sierra.
>> Basically the modal windows or dialogs, in these OSes simply does not work 
>> and this seems to happen since LC 6.7.x!
>> When you open a modal stack the expected behavior is that the script 
>> execution is interrupted and you cannot interact with the calling or other 
>> opened windows. While the first thing seems to happen, the second one 
>> doesn’t work: you can click on buttons, fields or any other control in the 
>> calling stack or any other stack opened.
>> I think that this is a very big problem mainly in porting applications from 
>> older versions of LC to the newest one and it’s quite strange that nobody 
>> else noticed this before or consider this a problem.
>> 
>> I already filed a bug report at 
>> https://quality.livecode.com/show_bug.cgi?id=22368 
>>  in which you can also 
>> find a demo stack to easily reproduce the behavior.
>> 
>> Anyone can comment on this? Are you experiencing this as a problem? Is there 
>> a workaround or a solution for this?
>> 
>> The problem seems not to be present on Mojave but I was not able to try on 
>> other versions on MacOS and it’s not present on Windows.
>> 
>> 
> 
> This one has been around for a while, and I thought it had been previously 
> reports (but still not fixed). I seem to recall there was a lengthy 
> discussion of it on the list a long time ago.
> 
> The work-around seems to be locking things down before calling an ask or 
> answer dialog (lock messages, lock your menus and so on) so that no other 
> user actions can start any other script.

___
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

Re: Weird behavior for modal stacks and answer dialogs

2019-09-09 Thread Tom Glod via use-livecode 
Yeah i remember getting really heated when this behaviior was
introduced. drove me nuts.

I think I just used a "wait while stack is open" kind of command (with
messages) and it works fine.


On Mon, Sep 9, 2019 at 7:31 AM Paul Dupuis via use-livecode <
use-livecode@lists.runrev.com> wrote:

> On 9/9/2019 6:50 AM, Giovanni via use-livecode wrote:
> > Hi everybody,
> > I’m writing here to report a very strange behavior of modal stacks and
> answer dialogs on MacOS Yosemite and Sierra.
> > Basically the modal windows or dialogs, in these OSes simply does not
> work and this seems to happen since LC 6.7.x!
> > When you open a modal stack the expected behavior is that the script
> execution is interrupted and you cannot interact with the calling or other
> opened windows. While the first thing seems to happen, the second one
> doesn’t work: you can click on buttons, fields or any other control in the
> calling stack or any other stack opened.
> > I think that this is a very big problem mainly in porting applications
> from older versions of LC to the newest one and it’s quite strange that
> nobody else noticed this before or consider this a problem.
> >
> > I already filed a bug report at
> https://quality.livecode.com/show_bug.cgi?id=22368 <
> https://quality.livecode.com/show_bug.cgi?id=22368> in which you can also
> find a demo stack to easily reproduce the behavior.
> >
> > Anyone can comment on this? Are you experiencing this as a problem? Is
> there a workaround or a solution for this?
> >
> > The problem seems not to be present on Mojave but I was not able to try
> on other versions on MacOS and it’s not present on Windows.
> >
> >
>
> This one has been around for a while, and I thought it had been
> previously reports (but still not fixed). I seem to recall there was a
> lengthy discussion of it on the list a long time ago.
>
> The work-around seems to be locking things down before calling an ask or
> answer dialog (lock messages, lock your menus and so on) so that no
> other user actions can start any other script.
>
> ___
> 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
>
___
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

Re: Weird behavior for modal stacks and answer dialogs

2019-09-09 Thread Paul Dupuis via use-livecode 

On 9/9/2019 6:50 AM, Giovanni via use-livecode wrote:

Hi everybody,
I’m writing here to report a very strange behavior of modal stacks and answer 
dialogs on MacOS Yosemite and Sierra.
Basically the modal windows or dialogs, in these OSes simply does not work and 
this seems to happen since LC 6.7.x!
When you open a modal stack the expected behavior is that the script execution 
is interrupted and you cannot interact with the calling or other opened 
windows. While the first thing seems to happen, the second one doesn’t work: 
you can click on buttons, fields or any other control in the calling stack or 
any other stack opened.
I think that this is a very big problem mainly in porting applications from 
older versions of LC to the newest one and it’s quite strange that nobody else 
noticed this before or consider this a problem.

I already filed a bug report at https://quality.livecode.com/show_bug.cgi?id=22368 
 in which you can also find 
a demo stack to easily reproduce the behavior.

Anyone can comment on this? Are you experiencing this as a problem? Is there a 
workaround or a solution for this?

The problem seems not to be present on Mojave but I was not able to try on 
other versions on MacOS and it’s not present on Windows.




This one has been around for a while, and I thought it had been 
previously reports (but still not fixed). I seem to recall there was a 
lengthy discussion of it on the list a long time ago.


The work-around seems to be locking things down before calling an ask or 
answer dialog (lock messages, lock your menus and so on) so that no 
other user actions can start any other script.


___
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

Weird behavior for modal stacks and answer dialogs

2019-09-09 Thread Giovanni via use-livecode 
Hi everybody,
I’m writing here to report a very strange behavior of modal stacks and answer 
dialogs on MacOS Yosemite and Sierra.
Basically the modal windows or dialogs, in these OSes simply does not work and 
this seems to happen since LC 6.7.x!
When you open a modal stack the expected behavior is that the script execution 
is interrupted and you cannot interact with the calling or other opened 
windows. While the first thing seems to happen, the second one doesn’t work: 
you can click on buttons, fields or any other control in the calling stack or 
any other stack opened.
I think that this is a very big problem mainly in porting applications from 
older versions of LC to the newest one and it’s quite strange that nobody else 
noticed this before or consider this a problem.

I already filed a bug report at 
https://quality.livecode.com/show_bug.cgi?id=22368 
 in which you can also find 
a demo stack to easily reproduce the behavior.

Anyone can comment on this? Are you experiencing this as a problem? Is there a 
workaround or a solution for this?

The problem seems not to be present on Mojave but I was not able to try on 
other versions on MacOS and it’s not present on Windows.

Regards!

--
Giovanni
___
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