| Re: MAP keyword [message #56633] |
Thu, 08 November 2007 16:06 |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
natha writes:
> Ok, I'm sorry for explanations..
>
> My interface is a normal interface with MBAR, buttons, TABS..
> It is really similar to Firefox...
>
> The only difference is that depending on the tab selected the buttons
> in the main menu change. I've got 2 different tabs and I want that
> when the user selects type 1 tab, the widget_base_1 with his
> corresponding buttons will be unmmaping and widget_base 2 with the
> other buttons set MAP=1..
> Thats all !
>
> The problem is that the widget_base_1 (containing the buttons for tabs
> type 1) is resized when I add a new tab. When I close a tab the
> resizing is more accentuated.
OK, I think I have a better idea of what you are doing
now. But I don't think I have much constructive to
offer. Clearly you are dealing here with what we call
the "natural width" of a base widget. Most of the time
when I'm confronted with this problem I add more base
widgets (with XPAD and YPAD set to 0) as organizers.
It is an iterative process, usually. After much to-ing
and fro-ing, I can usually get something that is close
to what I want.
In your case, much as I dislike saying it, you might
have to explicitly size some of your base widgets to
prevent them from jumping around on you.
Without seeing the actual code (which, under no
circumstance, do I want to do!) I can't offer anything
more helpful. Sorry.
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/
|
|
|
|
| Re: MAP keyword [message #56637 is a reply to message #56633] |
Thu, 08 November 2007 14:37  |
natha
Messages: 482
Registered: October 2007
|
Senior Member |
|
|
Ok, I'm sorry for explanations..
My interface is a normal interface with MBAR, buttons, TABS..
It is really similar to Firefox...
The only difference is that depending on the tab selected the buttons
in the main menu change. I've got 2 different tabs and I want that
when the user selects type 1 tab, the widget_base_1 with his
corresponding buttons will be unmmaping and widget_base 2 with the
other buttons set MAP=1..
Thats all !
The problem is that the widget_base_1 (containing the buttons for tabs
type 1) is resized when I add a new tab. When I close a tab the
resizing is more accentuated.
I hope you can understand my problem David !
Thanks !
|
|
|
|
| Re: MAP keyword [message #56638 is a reply to message #56637] |
Thu, 08 November 2007 14:15 |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
natha writes:
> My widget_base is initialized with MAP=0:
>
> self.ToolTipsBase=WIDGET_BASE(buttonsBase, FRAME=1, /ROW,
> SCR_YSIZE=35, /BASE_ALIGN_CENTER, MAP=0)
>
> In the interface, when a new file is opened I change this state via
> WIDGET_CONTROL:
>
> WIDGET_CONTROL, self.VPRToolTipsBase, MAP=1
Well, I'm confused. Is this the same widget as you
created above!?
> In this moment I dont have any problems.
> But then if I want to add a new WIDGET_TAB in the top level widget,
> self.ToolTipsBase is resized automaticly.
Resized to what? What would you want it to do? I'm not
sure it is a good idea to add another TAB widget after
the program has been realized. I can see how this could
cause confusion. But I don't see what this has to do
with your unmapped base, either. Is it in the unmapped
base that you are creating the tab widget?
Sorry, I just find the whole discussion confusing. :-(
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/
|
|
|
|
| Re: MAP keyword [message #56639 is a reply to message #56638] |
Thu, 08 November 2007 13:54 |
natha
Messages: 482
Registered: October 2007
|
Senior Member |
|
|
My widget_base is initialized with MAP=0:
self.ToolTipsBase=WIDGET_BASE(buttonsBase, FRAME=1, /ROW,
SCR_YSIZE=35, /BASE_ALIGN_CENTER, MAP=0)
In the interface, when a new file is opened I change this state via
WIDGET_CONTROL:
WIDGET_CONTROL, self.VPRToolTipsBase, MAP=1
In this moment I dont have any problems.
But then if I want to add a new WIDGET_TAB in the top level widget,
self.ToolTipsBase is resized automaticly.
In the IDL manual appears:
Under Microsoft Windows, when a hidden base is realized, then mapped,
a Windows resize message is sent by the windowing system. This "extra"
resize event is generated before any manipulation of the base widget
by the user.
But I use Linux.
|
|
|
|
| Re: MAP keyword [message #56640 is a reply to message #56639] |
Thu, 08 November 2007 13:38 |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
natha writes:
> I've a widget_base should be unmapped initially and when I set the
> map=1 with widget_control the widget_base is resized. why ?
>
> how can I do for solve this problem ?
What is the problem, exactly?
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
