Modal splitwindow?

Somewhere in my code, I open a splitwindow with a button. After some
values are set, users can go to the next step, or ignore the window
and continue without the values set. Works fine.

Now I include the same splitwindow in some other code where it is not
started from a button. This means of course that the window nicely
opens but the code using it values is executed before anything can be
chosen.

Is there a way to set, or simulate, a "modal splitwindow" so my
remaining steps wait (probably a limited time) until the user is ready
with the spiltwindow? I can't even set a wait loop before those next
steps and after opening the splitwindow because while that runs the
user can't done anything but ...wait, so he can not enter the
splitwindow either.


Dick van Kooten

Dick,
You can put a __Splitview control on a dialogwindow.
That way it is as modal as a dialog...


Erik

"D.J.W. van Kooten" <public@ic2remove.this.com> wrote in message
news:k54ob45dtil1hlmv294gtkd4crfn8i53oi@4ax.com...
> Somewhere in my code, I open a splitwindow with a button. After some
> values are set, users can go to the next step, or ignore the window
> and continue without the values set. Works fine.
>
> Now I include the same splitwindow in some other code where it is not
> started from a button. This means of course that the window nicely
> opens but the code using it values is executed before anything can be
> chosen.
>
> Is there a way to set, or simulate, a "modal splitwindow" so my
> remaining steps wait (probably a limited time) until the user is ready
> with the spiltwindow? I can't even set a wait loop before those next
> steps and after opening the splitwindow because while that runs the
> user can't done anything but ...wait, so he can not enter the
> splitwindow either.
>
>
> Dick van Kooten

On Mon, 1 Sep 2008 18:43:37 +0200, E®!k \\/!sser <nospam@nospam.com>
wrote:

>You can put a __Splitview control on a dialogwindow.
>That way it is as modal as a dialog...
>
>
Hello Erik,


That should be a possible solution, but the splitview control isn't
part of the available controls in the window os it's unusable. I
remember Robert once said he forgot to include it and I would rather
not wait until the end of the North American summer....

Dick

On Mon, 01 Sep 2008 18:02:33 +0200, D.J.W. van Kooten
<public@ic2remove.this.com> wrote:

I actually found a solution but I wonder if it could have been done
easier.

1. I split the method in part 1 and part 2
2. Part one opens the splitwindow, the call to part 2 is now in the
dispatch of the datawindow where it all happens
3. A class logic is set to false and as long as it is false, the
dispatch doesn't call part 2
4. When I close the splitwindow, the close method calls
oOwner:Setthislogicvar, oowner passed as a parameter to the
splitwindow and Setthislogicvar sets the class logic to true. As a
result, via the dispatch step2 is called.
5. As an option, I could add a start time and check on that too, so
the method continues when the user didn't do anything for a while

It works, but it would be handy to program this a bit more efficient.

Dick

Dick,

> That should be a possible solution, but the splitview control isn't
> part of the available controls in the window os it's unusable. I
> remember Robert once said he forgot to include it and I would rather
> not wait until the end of the North American summer....


Unusable? You can code it in the postinit of the window.
SELFSplitter :=
__SplitView{SELF,-1,Point{0,0},SELF:Size,TRUE,TRUE,SPLIT_VERTALIGN}

The spiltwindow class is build around this control, so you can have a look
in the SDK how you can take advantage of it.


Erik

On Mon, 1 Sep 2008 20:01:18 +0200, E®!k \\/!sser <nospam@nospam.com>
wrote:

Hello Erik,

>You can code it in the postinit of the window.
>SELFSplitter :=
>__SplitView{SELF,-1,Point{0,0},SELF:Size,TRUE,TRUE,SPLIT_VERTALIGN}

Good you've managed to find something about it! The new feature is
only documented in the What's new list. It is not only missing in the
control window but also absent in the help file so that's why I
considered it unusable.

Dick

Amusing definition of 'unusable' <g>.

I agree that its features are a little hidden and it still has bugs.
When used on tab controls it is frightful for resizing etc however it
can be forced to work.

It is very flexible now that it is unbundled to being a stand-alone
control but you just have to be careful about owners, menus and the
message pump. It will never be as good as the one with VS but it has
enhanced itself from the old enforced splitwindow construct.

Geoff



"D.J.W. van Kooten" <public@ic2remove.this.com> wrote in message
news:mukpb4dt7rmio6ld7odspoeq6gnue36q41@4ax.com:

> On Mon, 1 Sep 2008 20:01:18 +0200, ER!k \\/!sser <nospam@nospam.com>
> wrote:
>
> Hello Erik,
>
>
> >You can code it in the postinit of the window.
> >SELFSplitter :=
> >__SplitView{SELF,-1,Point{0,0},SELF:Size,TRUE,TRUE,SPLIT_VERTALIGN}
>
>
> Good you've managed to find something about it! The new feature is
> only documented in the What's new list. It is not only missing in the
> control window but also absent in the help file so that's why I
> considered it unusable.
>
> Dick