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

Bug 314748

Summary:	xgconf: names of new instances don't always stick; sometimes rename required
Product:	[Technology] RTSC	Reporter:	scott <sgrtsceclipse>
Component:	Core	Assignee:	Paul Gingrich <pgingrich>
Status:	CLOSED FIXED	QA Contact:
Severity:	critical
Priority:	P1	CC:	d-russo, dfriedland, sascha, sg
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:	target:3.30

Description scott

2010-05-27 14:32:38 EDT

When a new instance is created with xgconf (e.g., ti.sysbios.knl.Swi), even though the "name" property is defined, it is sometimes lost, and a global reference for the instance is *not* created.  To get this global reference, the instance must be selected again and "name" defined again.  This will cause the name to show properly in the "Outline" view, and a global reference to be created.  But the name field in the instance params still shows "null".

There seems to be some behavior threshold where this starts to work, and instance names start sticking upon first creation.  I haven't been able to find this condition.

Comment 1 David Friedland

2012-06-27 13:22:31 EDT

Scott, we are uncertain whether this has in fact been fixed.  Can you verify whether this problem is still extant?

Comment 2 Dave Russo

2014-02-16 11:35:07 EST

I believe this was fixed as part of the "hour glass" support during validation.

Comment 3 Paul Gingrich

2014-02-19 12:21:42 EST

Added code to cache value changes during validation, and to apply those changes after validation has completed.

Comment 4 Scott Gary

2014-03-19 19:39:39 EDT

This has apparently been fixed, I'm not able to recreate a failure.

Comment 5 Dave Russo

2015-02-14 22:39:35 EST

clean out old verified bugs