| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1057.1 | What wrong? | 4981::thomas | The Code Warrior | Tue Jul 04 1989 13:54 | 4 |
| >>The same happens
The same what? You never described what happens.
|
| 1057.2 | Really sorry... | PIOPPO::CARCANO | | Wed Jul 05 1989 03:35 | 18 |
| Well, something went wrong while including the text file: sorry!
What happens is that I get an ACCESS VIOLATION when calling XtUnrealizeWidget
but everything works fine with the Unmanage or Destroy calls (so, the widget
pointer doesn't seem to be the problem).
Now it makes sense to ask: which could be the reason for this "crash"?
Is there something I'm missing?
P.S.: I want to Unrealize a popup dialog box containing a lot of stext widgets.
Let's assume that the user, after having entered data in 5 out of 10 of the
stext fields wants to cancel the entire dialog box window. If I simply Unmanage
the widget, next time I manage it I find the 5 stext fields filled with the
previously entered data: I don't like this as well as I don't like to clear each
field from the callback considering that the field are about a hundred.
Sorry again and thanks,
Matteo
|
| 1057.3 | | LEOVAX::TREGGIARI | | Wed Jul 05 1989 12:01 | 24 |
| > Now it makes sense to ask: which could be the reason for this "crash"?
> Is there something I'm missing?
XtUnrealizeWidget has some problems in V1. These are fixed in V2.
Also in V2, popup dialog boxes have a new resource (DwtNautoUnrealize).
When set to TRUE (default is FALSE) the dialog box will unrealize itself
when it is unmanaged. This could be useful on non-virtual memory servers
as it will keep the window count lower (you can put *autoUnrealize: true
into your Xdefaults file).
> P.S.: I want to Unrealize a popup dialog box containing a lot of stext widgets.
> Let's assume that the user, after having entered data in 5 out of 10 of the
> stext fields wants to cancel the entire dialog box window. If I simply Unmanage
> the widget, next time I manage it I find the 5 stext fields filled with the
> previously entered data: I don't like this as well as I don't like to clear each
> field from the callback considering that the field are about a hundred.
Unfortunately, I don't think XtUnrealizeWidget will do what you want.
The intention of unrealizing is to destroy the window, but not to change
the state of the widget in any other way. That is the stext fields are still
going to be filled with the previously entered data.
Leo
|
| 1057.4 | Thanks a lot | AIDA::CARCANO | | Wed Jul 05 1989 12:33 | 12 |
| Leo,
thanks a lot for this answer and for the others you gave me in the past.
You are of great, great help.
P.S. From your reply it seems that the only way to do what I need
is to destroy the widget or clear field by field, right?
thanks again and ciao,
Matteo
|
| 1057.5 | | LEOVAX::TREGGIARI | | Wed Jul 05 1989 14:15 | 9 |
| > P.S. From your reply it seems that the only way to do what I need
> is to destroy the widget or clear field by field, right?
Right. Clearing field by field should be much more efficient than
having to re-create the widgets.
Leo
|
| 1057.6 | XtUnrealizeWidget work arounds?? | LARVAE::BULLARD | | Fri Aug 18 1989 05:53 | 10 |
| I have hit a problem with XtUnrealizeWidget.If I unrealize my
widget hierarchy and realize it again my Pulldown menus stop working
(maybe other widget do as well).I have tested this against version
2 and it appears to be fixed.The real problem is that Decwindows
V2 won't be available until Fy90 Q3 which is a problem for one
of my customers.Are there any work arounds?
regards Mark
|
| 1057.7 | | LEOVAX::TREGGIARI | | Sun Aug 20 1989 21:49 | 5 |
| I can't think of any work-around. What are they using it for?
Maybe there is an alternative way to accomplish the same thing...
Leo
|