Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 368837

Summary:	The protocol could make it easier to support native clients implementing the zIndex.
Product:	[RT] RAP	Reporter:	Johannes Eickhold <jeick>
Component:	RWT	Assignee:	Project Inbox <rap-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	ivan, jboehme, rsternberg
Version:	1.5
Target Milestone:	1.5 M5
Hardware:	All
OS:	All
Whiteboard:

Description Johannes Eickhold

2012-01-17 10:42:33 EST

Currently not every set or create operation in RAP's json protocol contains the zIndex property. This makes it somehow difficult to support stacking of overlapping widgets in native client implementationsusing the zIndex. Actually transfered zIndices currently start around 285.
Suggestion for enhancement: Maybe it is beneficial if every Composite widget (that contains other widgets) would transfer it children in a json array to inform the client of the zIndex property implicitly. The first entry position in the array would correspond to zIndices of the child widgets.

Comment 1 Ralf Sternberg

2012-01-17 12:11:28 EST

I agree that we should change the way z-order is synchronized.

In SWT, widgets doesn't have an explicit z-index. The z-order of a control is defined by its position in its parent's list of children. Hence, transmitting the z-index property in the protocol is more specific than actually needed.

Comment 2 Ivan Furnadjiev

2012-01-20 10:27:40 EST

Now, we a rendering a "children" property (array with ids) for every composite. The array order specify the zIndex - first control is on the top. Changes are in CVS HEAD.