[news.eclipse.platform.swt] Re: UI controls friendly with the workspace

["Andrei Serea" <andrei.serea@xxxxxx>]

Ed,

Yes, I guess I could easily do that, but I would also hate to do it since it 
would look nasty...I would have to pass aproximately 10 objects as 
parameters to the background job. And since I'm so into clean, readable and 
reusable code, I would sure like to use some classes as those from jdt.
Of course, I could just write them myself...it wouldn't take much time, but 
again...maybe someone knows about some public classes...

Thanks,
Andrei.

"Ed Merks" <merks@xxxxxxxxxx> wrote in message 
news:fvcigb$40f$1@xxxxxxxxxxxxxxxxxxxx
> Andrei,
>
> Couldn't you just pull the data out of the controls and pass it to the 
> background job?  I suppose you could use syncExec, but that seems kind of 
> gross...
>
>
> Andrei Serea wrote:
>> Hi all,
>>
>> I have came across a problem and I bet I'm not the only one: while 
>> creating a wizard for my own type of project, doing the usual workspace 
>> work (create the project and stuff), I wanted to access some controls to 
>> get info out of them...and surprize: invalid thread access.
>> Now, I have studied the way that the New Java Project Wizard does it and 
>> I saw that it uses some cool controls that store the info in a workspace 
>> thread friendly object (besides the widget itself). The only problem is 
>> that these classes are internal.. :(( (I'm talking about all the classes 
>> that extend 
>> org.eclipse.jdt.internal.ui.wizards.dialogfields.DialogField).
>> Here's the question: does anybody know about some controls that do the 
>> same but that are public???
>>
>> PS. If you ask me, I can't find a bloody reason for those classes to be 
>> internal in JDT...but that's just my two cents...
>>
>>