[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference bulova::decw_jan-89_to_nov-90

Title:DECWINDOWS 26-JAN-89 to 29-NOV-90
Notice:See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit
Moderator:STAR::VATNE
Created:Mon Oct 30 1989
Last Modified:Mon Dec 31 1990
Last Successful Update:Fri Jun 06 1997
Number of topics:3726
Total number of notes:19516

169.0. "DECwindows FT2, ISV needs answers" by MUNICH::ANDERMANN () Thu Feb 09 1989 11:43


	Hi,
	
	anybody out there looking for some sticky problems ?
	
	These 'bugs' , 'problems' or whatever they turn out to be were
	reported by one of out German ISV. They are pretty excited
	about DECwindows, especially about UIL.

	They're developing their stuff in an FT2 environment.
	I reproduced some of their errors on Ultrix 3.0 DW BL 10.4

	Here we go:

	1. Widgets are not positioned according to the x- and y- coordinates
	   in the UIL-File, but mostly placed at the default-position.

	2. A PopupDialogBox has the argument
	    	auto_unmanage 
	   which should cause the DialogBox to disappear after the 'dismiss'-
	   button is clicked. This doesn't happen. An extra call to
		XtUnmanageChild
	   is necessary

	3. Making a CautionBox a Child of DialogBox resultete in:
	      not all Widgets have same parent by XtManageChild
	   [note : I didn't see the source code, so I couldn't tell
	    whether their code is buggy, seems to me it is]

	4. A Listbox doesn't offer the possibility of a 'deselect'.
	   Any work-around ????????

	5. According to the manual an 'activate' reason is generated
	   when a PulldownEntry is activated. I couldn't catch it.
	   When selecting an item out of a PulldownMenue I only got
	   the 'activate' reason for the PushButton.

	   p.s.: What's the sense in getting an 'activate' for the 
	   	 PushButtonEntry ????????????????????

	That's it, folks.
	You can tell me anything you want (even yell at me or tell me
	to read my f*ing manuals [* stands for ascinat]), but I'm
	pretty grateful for any real help.

	Hans Andermann @ MUH DTN 756-1259	  

	   

T.RTitleUserPersonal
Name
DateLines
169.1Possible Answer for Coordinate ProblemVENOM::DLUGOSZRon Dlugosz, DTN 264-0306Thu Feb 09 1989 16:1513
    
       Its hard to tell from the description, but a common mistake is
       to position widgets within an attached dialog box using pixel
       coordinates, while the default positioning units are font units.
    
       If this is the situation then 
    
    		units = DwtPixelUnits
    
       should fix the problem.

    /ron    

169.2some partial answers and more questionsR2ME2::OBRYANWhen in doubt, let the user decide.Thu Feb 09 1989 17:5136
re:.0

>	1. Widgets are not positioned according to the x- and y- coordinates
>	   in the UIL-File, but mostly placed at the default-position.
Which widgets?  What type of parent does each widget have?  Many 'container'
widgets overrided (by default) the x,y,width and height of their children.

>	2. A PopupDialogBox has the argument
>	    	auto_unmanage 
>	   which should cause the DialogBox to disappear after the 'dismiss'-
>	   button is clicked. This doesn't happen. An extra call to
>		XtUnmanageChild
>	   is necessary
Has this argument been explicitly set TRUE at create time?  If so, then
this is unusual behavior.

>	3. Making a CautionBox a Child of DialogBox resultete in:
>	      not all Widgets have same parent by XtManageChild
>	   [note : I didn't see the source code, so I couldn't tell
>	    whether their code is buggy, seems to me it is]
A caution_box is a 'popup' style widgets.  These widgets, if declared
as children of another widget, must be declared 'unmanaged' in the UIL
'controls' section.  After Fetching the parent, you must then XtManage
the popup-child.

>	   p.s.: What's the sense in getting an 'activate' for the 
>	   	 PushButtonEntry ????????????????????
Do you mean the PullDownEntry?  If so, then this activate is called when
a button is released in the Entry itself.  An application may wish to take
some default action on the up-click on the Entry, even though the normal
user behavior would be to release the button within a child of the Entry
(usually a pulldown_menu.)

Michael