| Re: No, no, not again! [message #13480] |
Tue, 17 November 1998 00:00 |
steinhh
Messages: 260
Registered: June 1994
|
Senior Member |
|
|
In article <MPG.10bb10ccfad542209896da@news.frii.com>
davidf@dfanning.com (David Fanning) writes:
> David Foster (foster@bial1.ucsd.edu) writes:
>
>> Along these same lines, I have always disliked the limitation that
>> you can only use the WIDGET_BASE(..., MBAR=menu_widID ) keyword
>> for top-level base widgets. This precludes the use of this handy
>> feature for any widget that might need to be called from within
>> another widget...quite a limitation in my opinion.
>
> I don't understand what you mean by "any widget that might
> need to be called from within another widget". Can you
> elaborate? Certainly any widget program that has its
> own top-level base can have a menu bar and be called
> from any other widget program. I'm confused by what you
> mean.
I think David Foster just dropped one or two qualifiers, but then his
statement is correct: "any (potentially modal) widget that might need
to be called from within another widget". "Potentially modal" here
means "modal if called from within another widget".
From the widget_base online documentation (MBAR keyword):
Caution You cannot specify both the MBAR and MODAL keywords for
the same widget. Doing so will cause an error.
Also, modal widgets cannot be scrollable.
Regards,
Stein Vidar
|
|
|
|
| Re: No, no, not again! [message #13482 is a reply to message #13480] |
Tue, 17 November 1998 00:00  |
davidf
Messages: 2866
Registered: September 1996
|
Senior Member |
|
|
David Foster (foster@bial1.ucsd.edu) writes:
> Along these same lines, I have always disliked the limitation that
> you can only use the WIDGET_BASE(..., MBAR=menu_widID ) keyword
> for top-level base widgets. This precludes the use of this handy
> feature for any widget that might need to be called from within
> another widget...quite a limitation in my opinion.
I don't understand what you mean by "any widget that might
need to be called from within another widget". Can you
elaborate? Certainly any widget program that has its
own top-level base can have a menu bar and be called
from any other widget program. I'm confused by what you
mean.
Cheers,
David
|
|
|
|
| Re: No, no, not again! [message #13484 is a reply to message #13480] |
Mon, 16 November 1998 00:00 |
David Foster
Messages: 341
Registered: January 1996
|
Senior Member |
|
|
Stein Vidar Hagfors Haugan wrote:
>
> <Rant mode on>
>
> Sadly, I just discovered (yet) another one of these instances. The
> "new and improved" handling of modal widgets is the culprit in this
> case.
>
> Modality used to be the method of choice whenever a widget program
> needed to return something - this made sure the widget program didn't
> "fall through" the XMANAGER call and return before the answer was
> finished - no matter how complex the task.
>
> With the old system (xmanager,....,/modal), modal widgets could have
> any level of complexity - no questions asked. With the "new and
> improved" system (widget_base(...,/modal)), RSI has changed the
> meaning of modality!
>
<more comments and example code snipped>
Along these same lines, I have always disliked the limitation that
you can only use the WIDGET_BASE(..., MBAR=menu_widID ) keyword
for top-level base widgets. This precludes the use of this handy
feature for any widget that might need to be called from within
another widget...quite a limitation in my opinion.
Was this done to make this compatible with Windoze? Please say
it ain't so!
Dave
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~
David S. Foster Univ. of California, San Diego
Programmer/Analyst Brain Image Analysis Laboratory
foster@bial1.ucsd.edu Department of Psychiatry
(619) 622-5892 8950 Via La Jolla Drive, Suite 2240
La Jolla, CA 92037
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
