Conference bulova::decw_jan-89_to_nov-90

2556.0. "popup_attached_db and selection" by BRSDVP::ROETS () Mon Apr 02 1990 10:02

Hello guys,

I have a little question :

I have a popup_attached_db that controls a selection widget as follows :


object
    w_p_a_d_get_select : popup_attached_db {
       arguments {
           x      = 100;
           y      = 100;
           width  = 283;
           height = 261;
           style = DwtModeless;
           title = ccs_get_select;
       };
       controls {
           selection       w_s_get;
           push_button     w_p_b_cancel_get_select;
       };
    };

object
    w_s_get : selection {
       arguments {
           x                   = ci_normal_offset;
           y                   = ci_normal_offset;
           style               = DwtModal;
           no_resize           = false;
           default_position    = true;
         };
       callbacks {
           cancel = procedure cancel_button_activate;
       };
         
    };

object
    w_p_b_cancel_get_select : push_button {
       arguments {
           label_label          = ccs_cancel;
       };
       callbacks {
           activate = procedure cancel_button_activate;
       };
    };

end module;


When I use thios in an application, The selection widget gets managed
before the popup_attached_db, and I get the message
Not all children have the same parent.
When I use a selection box only, it works fine.

What can be the problem.
Is it reasonable that a popup_attached_dialog box controls
a selection (which is a popup widget to...?).
It is possible according to the manuals, however it does not work
I think.
If I am doing something wrong please tell me.

Thanks in advance,

Chris Roets
    
               

    The problem (and I guess it's DRM's problem) is that the push button
    and the selection box don't have the same parent.  That's because
    the toolkit inserts a "hidden shell" as the parent of any type of
    popup dialog box (including selection).  If you declare the selection
    box as unmanaged in your UIL file, and then manally XtManageChild
    it in your code, you should be able to get around the problem.
    
    Leo