Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 313272 - Calling Tree.setEnabled() upon view creation causes crash.
Summary: Calling Tree.setEnabled() upon view creation causes crash.
Status: RESOLVED INVALID
Alias: None
Product: RAP
Classification: RT
Component: RWT (show other bugs)
Version: 1.3   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2010-05-17 21:58 EDT by Austin Riddle CLA
Modified: 2010-05-18 10:32 EDT (History)
0 users

See Also:


Attachments
Sample project illustrating problem (445.52 KB, application/x-zip-compressed)
2010-05-17 21:58 EDT, Austin Riddle CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Austin Riddle CLA 2010-05-17 21:58:46 EDT
Created attachment 168850 [details]
Sample project illustrating problem

Using 1.3 M7

Steps to reproduce:

1. Create a view with a tree viewer.
2. Set the tree to setEnabled(false) in createPartControl().
3. Run the app and observe a crash.

I have tested this with IE, Firefox and Chrome and they all give the following error:


Error in property textColor of class qx.ui.layout.HorizontalBoxLayout in method styleTextColor with incoming value 'widget.graytext': Is invalid!


I originally experienced this only in IE in my application, and with an "Invalid Argument" error instead of the one above.  But when attempting to reproduce in a bug demo, I received the error above.  

The sample view loaded by default in the bug-demo project is called IconTreeView.java
Comment 1 Ivan Furnadjiev CLA 2010-05-18 03:09:45 EDT
Hi Austin, maybe it is strange, but I can't reproduce the bug with your demo project and CVS HEAD. Tested on Windows 7, IE8, FF 3.6.3, Chrome 6.0.401.1 beta. All work just fine, view is loaded and tree is disabled. Any special hints how to reproduce it?
Comment 2 Austin Riddle CLA 2010-05-18 10:32:14 EDT
(In reply to comment #1)

After some more digging it turns out that I had a modification to AppearancesBase.js that was causing the error.  Sorry for the trouble.