Re: modal window = block handler?

2017-07-11 Thread Lagi Pittas via use-livecode
I second that emotion.

And this shouldn't  cause any regressions or refactoring - should be
announced  by thursday then? ;-)

Lagi

On 10 July 2017 at 22:53, Paul Dupuis via use-livecode <
use-livecode@lists.runrev.com> wrote:

> On 7/10/2017 4:54 PM, J. Landman Gay via use-livecode wrote:
> > On 7/10/17 3:41 PM, J. Landman Gay via use-livecode wrote:
> >> On 7/10/17 12:18 PM, FlexibleLearning.com via use-livecode wrote:
> >>> Opening a modal as normal (i.e. visible) obviously still does what you
> >>> specify. We simply have a 'hidden feature' that enables a
> >>> non-blocking modal
> >>> should it be required (e.g. a progress indicator that prevents
> >>> user-clicks
> >>> on other windows).
> >>
> >> This is no longer true and affects all stacks that require a modal to
> >> block other windows. "Modal" should mean no other actions are
> >> possible until the modal is dismissed.
> >>
> >> The command: modal "stackname" allows the user to click on another
> >> window and bring it to the front, and then proceed normally as though
> >> the modal didn't exist.
> >>
> >
> > I've added a test stack and comment to
> > http://quality.livecode.com/show_bug.cgi?id=14275
> >
>
> Whatever LiveCode chooses to call them, as developer I (and I think
> "we") need TWO behaviors for modal windows:
>
> 1) present the window and halt the current script on the line that
> presented the window and prevent any other scripts or actions from
> executing until that is closed
>
> 2) present a modal windows, allow no other scripts or actions to occur,
> but allow the current handler to continue executing.
>
> This would allow for traditional modal dialogs (1) and modal progress
> indicators (2)
>
>
>
> ___
> 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: modal window = block handler?

2017-07-10 Thread Paul Dupuis via use-livecode
I realize that, but this thread has been discussing whether that is a
"bug" or not. I support that there should be a feature, but probably a
MORE clearly identified feature. Something LIKE (I am not proposing
specific syntax, but illustrating a point)

open window "X" as modal paused
and
open window "X" as modal continue

would be clearer that remembering you have to open the model dialog
invisible and then show it.


On 7/10/2017 7:26 PM, Bob Sneidar via use-livecode wrote:
> According to this thread, that is what open invis as modal does. 
>
> Bob S
>
>
>> On Jul 10, 2017, at 14:53 , Paul Dupuis via use-livecode 
>>  wrote:
>>
>> 2) present a modal windows, allow no other scripts or actions to occur,
>> but allow the current handler to continue executing.
>
> ___
> 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: modal window = block handler?

2017-07-10 Thread Bob Sneidar via use-livecode
According to this thread, that is what open invis as modal does. 

Bob S


> On Jul 10, 2017, at 14:53 , Paul Dupuis via use-livecode 
>  wrote:
> 
> 2) present a modal windows, allow no other scripts or actions to occur,
> but allow the current handler to continue executing.


___
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: modal window = block handler?

2017-07-10 Thread Paul Dupuis via use-livecode
On 7/10/2017 4:54 PM, J. Landman Gay via use-livecode wrote:
> On 7/10/17 3:41 PM, J. Landman Gay via use-livecode wrote:
>> On 7/10/17 12:18 PM, FlexibleLearning.com via use-livecode wrote:
>>> Opening a modal as normal (i.e. visible) obviously still does what you
>>> specify. We simply have a 'hidden feature' that enables a
>>> non-blocking modal
>>> should it be required (e.g. a progress indicator that prevents
>>> user-clicks
>>> on other windows).
>>
>> This is no longer true and affects all stacks that require a modal to
>> block other windows. "Modal" should mean no other actions are
>> possible until the modal is dismissed.
>>
>> The command: modal "stackname" allows the user to click on another
>> window and bring it to the front, and then proceed normally as though
>> the modal didn't exist.
>>
>
> I've added a test stack and comment to
> http://quality.livecode.com/show_bug.cgi?id=14275
>

Whatever LiveCode chooses to call them, as developer I (and I think
"we") need TWO behaviors for modal windows:

1) present the window and halt the current script on the line that
presented the window and prevent any other scripts or actions from
executing until that is closed

2) present a modal windows, allow no other scripts or actions to occur,
but allow the current handler to continue executing.

This would allow for traditional modal dialogs (1) and modal progress
indicators (2)



___
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: modal window = block handler?

2017-07-10 Thread Bob Sneidar via use-livecode
err... will NOW work?

Bob S


> On Jul 10, 2017, at 14:08 , Bob Sneidar via use-livecode 
>  wrote:
> 
> Okay, this has piqued my curiosity. Are you saying that if I open a stack 
> invisible as modal, I can then show that stack later and animated progress 
> indicators will not work?? 
> 
> Bob S


___
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: modal window = block handler?

2017-07-10 Thread Bob Sneidar via use-livecode
Okay, this has piqued my curiosity. Are you saying that if I open a stack 
invisible as modal, I can then show that stack later and animated progress 
indicators will not work?? 

Bob S


> On Jul 10, 2017, at 13:51 , FlexibleLearning.com via use-livecode 
>  wrote:
> 
> If “popup” is non-blocking then it’s a bug. However, I hope that the 
> non-blocking behaviour of “open invis as modal” is retained, or there is no 
> way to indicate progress in a modal.
> 
> 
> 
> Hugh Senior
> 
> FLCo

___
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: modal window = block handler?

2017-07-10 Thread J. Landman Gay via use-livecode

On 7/10/17 3:41 PM, J. Landman Gay via use-livecode wrote:

On 7/10/17 12:18 PM, FlexibleLearning.com via use-livecode wrote:

Opening a modal as normal (i.e. visible) obviously still does what you
specify. We simply have a 'hidden feature' that enables a non-blocking 
modal
should it be required (e.g. a progress indicator that prevents 
user-clicks

on other windows).


This is no longer true and affects all stacks that require a modal to 
block other windows. "Modal" should mean no other actions are possible 
until the modal is dismissed.


The command: modal "stackname" allows the user to click on another 
window and bring it to the front, and then proceed normally as though 
the modal didn't exist.




I've added a test stack and comment to 
http://quality.livecode.com/show_bug.cgi?id=14275


--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com

___
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: modal window = block handler?

2017-07-10 Thread FlexibleLearning.com via use-livecode
If “popup” is non-blocking then it’s a bug. However, I hope that the 
non-blocking behaviour of “open invis as modal” is retained, or there is no way 
to indicate progress in a modal.

 

Hugh Senior

FLCo

 

From: Andre Garzia [mailto:an...@andregarzia.com] 
Sent: 10 July 2017 19:15
To: How to use LiveCode <use-livecode@lists.runrev.com>
Cc: FlexibleLearning.com <ad...@flexiblelearning.com>
Subject: Re: modal window = block handler?

 

Friends,

 

Just to add a related note here, at least on 9dp5 the "popup" command is also 
not pausing. It is supposed to pause the handler that calls it until menupick 
happens but in my experience here it simple keeps running even while the modal 
is open.

 

This might be related.

 

om om

andre

 

On Mon, Jul 10, 2017 at 2:18 PM, FlexibleLearning.com via use-livecode 
<use-livecode@lists.runrev.com <mailto:use-livecode@lists.runrev.com> > wrote:

Opening a modal as normal (i.e. visible) obviously still does what you
specify. We simply have a 'hidden feature' that enables a non-blocking modal
should it be required (e.g. a progress indicator that prevents user-clicks
on other windows).

Hugh Senior
FLCo

> I'm going to have to disagree here. I open windows modally for the
specific
> purpose of halting code in the calling stack until the modal window is
> dismissed so that I can proceed with input from the user. An Answer dialog
is
> simply a modal stack if I am not mistaken. It's interesting though that a
> hidden window is not modal. I will have to experiment with that.
>
> Bob S
>
>
> > On Jul 10, 2017, at 24:03 , FlexibleLearning.com via use-livecode  livec...@lists.runrev.com <mailto:livec...@lists.runrev.com> > wrote:
> >
> > (modal blocks underlying windows, not necessarily code)



___
use-livecode mailing list
use-livecode@lists.runrev.com <mailto: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




-- 

http://www.andregarzia.com -- All We Do Is Code.
http://fon.nu -- minimalist url shortening service.

___
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: modal window = block handler?

2017-07-10 Thread J. Landman Gay via use-livecode

On 7/10/17 12:18 PM, FlexibleLearning.com via use-livecode wrote:

Opening a modal as normal (i.e. visible) obviously still does what you
specify. We simply have a 'hidden feature' that enables a non-blocking modal
should it be required (e.g. a progress indicator that prevents user-clicks
on other windows).


This is no longer true and affects all stacks that require a modal to 
block other windows. "Modal" should mean no other actions are possible 
until the modal is dismissed.


The command: modal "stackname" allows the user to click on another 
window and bring it to the front, and then proceed normally as though 
the modal didn't exist.


--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com

___
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: modal window = block handler?

2017-07-10 Thread Bob Sneidar via use-livecode
EEEK!

> On Jul 10, 2017, at 11:15 , Andre Garzia via use-livecode 
>  wrote:
> 
> Friends,
> 
> Just to add a related note here, at least on 9dp5 the "popup" command is
> also not pausing. It is supposed to pause the handler that calls it until
> menupick happens but in my experience here it simple keeps running even
> while the modal is open.
> 
> This might be related.
> 
> om om
> andre


___
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: modal window = block handler?

2017-07-10 Thread Andre Garzia via use-livecode
Friends,

Just to add a related note here, at least on 9dp5 the "popup" command is
also not pausing. It is supposed to pause the handler that calls it until
menupick happens but in my experience here it simple keeps running even
while the modal is open.

This might be related.

om om
andre

On Mon, Jul 10, 2017 at 2:18 PM, FlexibleLearning.com via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Opening a modal as normal (i.e. visible) obviously still does what you
> specify. We simply have a 'hidden feature' that enables a non-blocking
> modal
> should it be required (e.g. a progress indicator that prevents user-clicks
> on other windows).
>
> Hugh Senior
> FLCo
>
> > I'm going to have to disagree here. I open windows modally for the
> specific
> > purpose of halting code in the calling stack until the modal window is
> > dismissed so that I can proceed with input from the user. An Answer
> dialog
> is
> > simply a modal stack if I am not mistaken. It's interesting though that a
> > hidden window is not modal. I will have to experiment with that.
> >
> > Bob S
> >
> >
> > > On Jul 10, 2017, at 24:03 , FlexibleLearning.com via use-livecode  > livec...@lists.runrev.com> wrote:
> > >
> > > (modal blocks underlying windows, not necessarily code)
>
>
> ___
> 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
>



-- 
http://www.andregarzia.com -- All We Do Is Code.
http://fon.nu -- minimalist url shortening service.
___
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: modal window = block handler?

2017-07-10 Thread FlexibleLearning.com via use-livecode
Opening a modal as normal (i.e. visible) obviously still does what you
specify. We simply have a 'hidden feature' that enables a non-blocking modal
should it be required (e.g. a progress indicator that prevents user-clicks
on other windows).

Hugh Senior
FLCo

> I'm going to have to disagree here. I open windows modally for the
specific
> purpose of halting code in the calling stack until the modal window is
> dismissed so that I can proceed with input from the user. An Answer dialog
is
> simply a modal stack if I am not mistaken. It's interesting though that a
> hidden window is not modal. I will have to experiment with that.
> 
> Bob S
> 
> 
> > On Jul 10, 2017, at 24:03 , FlexibleLearning.com via use-livecode  livec...@lists.runrev.com> wrote:
> >
> > (modal blocks underlying windows, not necessarily code)


___
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: modal window = block handler?

2017-07-10 Thread Tom Glod via use-livecode
lesson learned .. happy i found out about this inconcistency now rather
than later.

going forward I am using a "wait until mywindowopen = 0 with messages" to
make sure i get the same identical behavior on every platform.

thanks as always you guys

On Mon, Jul 10, 2017 at 11:18 AM, Bob Sneidar via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Of course, modal windows do not "halt code execution" in that sense. They
> could not because you would not be able to use any code in front or back
> scripts. They prevent the calling handler from proceeding. It's like
> inserting blocking code where the modal is called.
>
> Bob S
>
>
> > On Jul 10, 2017, at 08:16 , Paul Dupuis via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >
> > A related issue I ran into recently:
> >
> > I had a complex modal dialog. In my code for the dialog controls I was
> > calling a routine that had a "wait 0 with messages" statement. I
> > discovered that the wait ... with messages allows user events (for
> > example commandKeyDown, etc.)  to kick off other scripts while the modal
> > dialog was still active under OSX. Windows still does a better job of
> > modal actually being modal. This was an older stack under LC6.7.11, so I
> > am not sure if the this is also applies to more recent versions.
>
>
> ___
> 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: modal window = block handler?

2017-07-10 Thread Bob Sneidar via use-livecode
Of course, modal windows do not "halt code execution" in that sense. They could 
not because you would not be able to use any code in front or back scripts. 
They prevent the calling handler from proceeding. It's like inserting blocking 
code where the modal is called. 

Bob S


> On Jul 10, 2017, at 08:16 , Paul Dupuis via use-livecode 
>  wrote:
> 
> A related issue I ran into recently:
> 
> I had a complex modal dialog. In my code for the dialog controls I was
> calling a routine that had a "wait 0 with messages" statement. I
> discovered that the wait ... with messages allows user events (for
> example commandKeyDown, etc.)  to kick off other scripts while the modal
> dialog was still active under OSX. Windows still does a better job of
> modal actually being modal. This was an older stack under LC6.7.11, so I
> am not sure if the this is also applies to more recent versions.


___
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: modal window = block handler?

2017-07-10 Thread Paul Dupuis via use-livecode
A related issue I ran into recently:

I had a complex modal dialog. In my code for the dialog controls I was
calling a routine that had a "wait 0 with messages" statement. I
discovered that the wait ... with messages allows user events (for
example commandKeyDown, etc.)  to kick off other scripts while the modal
dialog was still active under OSX. Windows still does a better job of
modal actually being modal. This was an older stack under LC6.7.11, so I
am not sure if the this is also applies to more recent versions.



On 7/10/2017 10:44 AM, Bob Sneidar via use-livecode wrote:
> I'm going to have to disagree here. I open windows modally for the specific 
> purpose of halting code in the calling stack until the modal window is 
> dismissed so that I can proceed with input from the user. An Answer dialog is 
> simply a modal stack if I am not mistaken. It's interesting though that a 
> hidden window is not modal. I will have to experiment with that. 
>
> Bob S
>
>
>> On Jul 10, 2017, at 24:03 , FlexibleLearning.com via use-livecode 
>>  wrote:
>>
>> (modal blocks underlying windows, not necessarily code)
>
> ___
> 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: modal window = block handler?

2017-07-10 Thread Bob Sneidar via use-livecode
I'm going to have to disagree here. I open windows modally for the specific 
purpose of halting code in the calling stack until the modal window is 
dismissed so that I can proceed with input from the user. An Answer dialog is 
simply a modal stack if I am not mistaken. It's interesting though that a 
hidden window is not modal. I will have to experiment with that. 

Bob S


> On Jul 10, 2017, at 24:03 , FlexibleLearning.com via use-livecode 
>  wrote:
> 
> (modal blocks underlying windows, not necessarily code)


___
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: modal window = block handler?

2017-07-10 Thread FlexibleLearning.com via use-livecode
If you open invisible, then display it, a modal will not block. This
non-modal behaviour of a modal has been incredibly useful for displaying a
progress  indicator in a modal window. I do not consider it a bug as such
(modal blocks underlying windows, not necessarily code), and would hope this
quirk remains available. Otherwise we would need something like "go stack as
modal with messages".

2p

Hugh Senior

> Hi everyone, i only recently switched to v8 ..and have found out that in
> this version, opening a modal window does not block the handler that
> opened
> it (until the window closes)  did that used to be a bug that is fixed
> now? is it a bug now? or was it a purposeful change in the engine?
> anyone familiar with this?
> 
> Thanks,
> 
> Tom


___
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: modal window = block handler?

2017-07-09 Thread Richard Gaskin via use-livecode

Tom Glod wrote:

> omg its actually doing it ... the correction to the type did not
> solve it.
>
> its continuing to run the handler after the stack is opened as modal.
>
> not good.

Does it help if you change:

  open stack "MyStack" as modal

...to:

  modal "MyStack"

?

- rg

___
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: modal window = block handler?

2017-07-09 Thread Tom Glod via use-livecode
no spotify

On Sun, Jul 9, 2017 at 4:12 PM, Tom Glod  wrote:

> omg its actually doing it ... the correction to the type did not solve it.
>
> its continuing to run the handler after the stack is opened as modal.
>
> not good.
>
> On Sun, Jul 9, 2017 at 4:08 PM, Tom Glod  wrote:
>
>> its on windows.i did a workaround for it .
>> for sure it was continuing the handler after opening the window ..
>>
>> BUT
>>
>> i did find that there was a space missing between the name of the stack
>> and "as modal"
>>
>> i didn't get an error from the engine ...so i never notice it before.
>>
>> i haven't gone back to check  stand by I will report back.
>>
>> On Sun, Jul 9, 2017 at 3:07 PM, Bob Sneidar via use-livecode <
>> use-livecode@lists.runrev.com> wrote:
>>
>>> Read further I am not using spotify.
>>>
>>> Bob S
>>>
>>> > On Jul 9, 2017, at 12:05 , Bob Sneidar via use-livecode <
>>> use-livecode@lists.runrev.com> wrote:
>>> >
>>> > That is remarkable. I am running V8 and modal windows work for me. Put
>>> a brealpoint right aftr the call to the modal stack and see if the
>>> breakpoint triggers.
>>> >
>>> > Bob S
>>>
>>>
>>> ___
>>> 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: modal window = block handler?

2017-07-09 Thread Tom Glod via use-livecode
omg its actually doing it ... the correction to the type did not solve it.

its continuing to run the handler after the stack is opened as modal.

not good.

On Sun, Jul 9, 2017 at 4:08 PM, Tom Glod  wrote:

> its on windows.i did a workaround for it .
> for sure it was continuing the handler after opening the window ..
>
> BUT
>
> i did find that there was a space missing between the name of the stack
> and "as modal"
>
> i didn't get an error from the engine ...so i never notice it before.
>
> i haven't gone back to check  stand by I will report back.
>
> On Sun, Jul 9, 2017 at 3:07 PM, Bob Sneidar via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>
>> Read further I am not using spotify.
>>
>> Bob S
>>
>> > On Jul 9, 2017, at 12:05 , Bob Sneidar via use-livecode <
>> use-livecode@lists.runrev.com> wrote:
>> >
>> > That is remarkable. I am running V8 and modal windows work for me. Put
>> a brealpoint right aftr the call to the modal stack and see if the
>> breakpoint triggers.
>> >
>> > Bob S
>>
>>
>> ___
>> 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: modal window = block handler?

2017-07-09 Thread Tom Glod via use-livecode
its on windows.i did a workaround for it .
for sure it was continuing the handler after opening the window ..

BUT

i did find that there was a space missing between the name of the stack and
"as modal"

i didn't get an error from the engine ...so i never notice it before.

i haven't gone back to check  stand by I will report back.

On Sun, Jul 9, 2017 at 3:07 PM, Bob Sneidar via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Read further I am not using spotify.
>
> Bob S
>
> > On Jul 9, 2017, at 12:05 , Bob Sneidar via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >
> > That is remarkable. I am running V8 and modal windows work for me. Put a
> brealpoint right aftr the call to the modal stack and see if the breakpoint
> triggers.
> >
> > Bob S
>
>
> ___
> 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: modal window = block handler?

2017-07-09 Thread Bob Sneidar via use-livecode
Read further I am not using spotify. 

Bob S

> On Jul 9, 2017, at 12:05 , Bob Sneidar via use-livecode 
>  wrote:
> 
> That is remarkable. I am running V8 and modal windows work for me. Put a 
> brealpoint right aftr the call to the modal stack and see if the breakpoint 
> triggers. 
> 
> Bob S


___
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: modal window = block handler?

2017-07-09 Thread Bob Sneidar via use-livecode
That is remarkable. I am running V8 and modal windows work for me. Put a 
brealpoint right aftr the call to the modal stack and see if the breakpoint 
triggers. 

Bob S


> On Jul 9, 2017, at 08:49 , Tom Glod via use-livecode 
>  wrote:
> 
> Hi everyone, i only recently switched to v8 ..and have found out that in
> this version, opening a modal window does not block the handler that opened
> it (until the window closes)  did that used to be a bug that is fixed
> now? is it a bug now? or was it a purposeful change in the engine?
> anyone familiar with this?
> 
> Thanks,
> 
> Tom


___
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: modal window = block handler?

2017-07-09 Thread Malte Pfaff-Brill via use-livecode
Out of curiosity: Is this on a Mac? Do you have Spotify open?

http://quality.livecode.com/show_bug.cgi?id=14275 


Cheers,

Malte

___
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


modal window = block handler?

2017-07-09 Thread Tom Glod via use-livecode
Hi everyone, i only recently switched to v8 ..and have found out that in
this version, opening a modal window does not block the handler that opened
it (until the window closes)  did that used to be a bug that is fixed
now? is it a bug now? or was it a purposeful change in the engine?
anyone familiar with this?

Thanks,

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