[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

2731.0. "Solutions to Application Overhead" by FREZEN::PROJECTS () Tue May 08 1990 18:13

	Decwindows is nice but...

	How do I get rid of all the nasty overhead produced by some of the
	widget configurations programmers are susceptible to creating?

	For instance I got a grid of simple text widgets... a left side and a
	right side.
			---------------------------
		        |            |            |
		        ---------------------------
			|            |            |
			---------------------------
			.	.	.
			.	.	.
			.	.	.
	And it goes down for 100-250 rows. Well it serves as a grid to
	execute com files and I highlight the currently active com file
	that is executing. This highlighting never reflects the active
	entry executing because of the decwindows overhead being beaten
	out to the X Queue by other AST's and X-events that are running
	simultaneously. I am routing all events (even ones performed in AST's)
	thru tghe X queue for synchronization for my medium sized application
	100-300k bytes of code.

	Does anyone know of any or all solutions that exist to alleviate
	overhead produced by applications.

	Any and all replies... thank you

T.R Title User Personal
Name Date Lines

2731.1 options... R2ME2::OBRYAN Tue May 08 1990 18:55 15

T.R	Title	User	Personal Name	Date	Lines
2731.1	options...	R2ME2::OBRYAN		`Tue May 08 1990 18:55`	15
	re:.0 If performance is a big issue, there are a couple of ways to improve the overhead due to the toolkit: 1. Turn all of your text widgets into label gadgets. (Memory consumption drops dramatically.) This will mean that the user will not be able to enter data directly into a field, but you can "pop up" a simple text widget when a user clicks on a field, transferring the text to the label gadget when the user has completed the entry. (Push button gadgets are also cheap.) 2. Use the VList widget. (Sources available from DECWIN::KLEIN.) (See DW_EXAMPLES conference for other useful widgets.) Michael

re:.0

If performance is a big issue, there are a couple of ways to improve the
overhead due to the toolkit:
	1. Turn all of your text widgets into label gadgets.  (Memory
	consumption drops dramatically.)  This will mean that the user
	will not be able to enter data directly into a field, but you
	can "pop up" a simple text widget when a user clicks on a field,
	transferring the text to the label gadget when the user has
	completed the entry.  (Push button gadgets are also cheap.)
	2. Use the VList widget.  (Sources available from DECWIN::KLEIN.)
	(See DW_EXAMPLES conference for other useful widgets.)

Michael