For the installation case, I can see two possibilities
1) opening the wizard again when an error is detected
2) don't let the user click the install button until the proper things have
been selected. This means that the validation is done as the user selects
and unselects things in the UI.
The
John said:
It would be nice if there as an unobtrusive way to let the user know
though - such as a trim widget that gets an error overlay added.
this is similar to the path I am exploring.
To clarify - you'll never get told of an update if you don't have the pref
on. The pref guides how often
Hi team,
ha~It seems my homework not enough, why I just miss Alex Blewitt's article
at
http://www.eclipsezone.org/eclipse/forums/t99762.html.
OK, the thread seems not a question.
The true question is that, since the main thread mode IApplications cannot
running, Why AppCommans not report a error
The webpage is not up-to-date, here is what it should say:
Whereas jar delta is based around the understanding of how a jar is shaped,
full delta works on any kind of file independently of what they contain.
- The processing steps to create the delta and reconstitute the final jars
are in place.
I think you may have run into bug
https://bugs.eclipse.org/bugs/show_bug.cgi?id=198988
Tom
From: 向雅 [EMAIL PROTECTED]
Thanks Thomas. I think I got it.
2008/2/14, Thomas Watson [EMAIL PROTECTED]:
I think you may have run into bug
https://bugs.eclipse.org/bugs/show_bug.cgi?id=198988
Tom
[image: Inactive hide details for 向雅 ---02/13/2008 01:21:30 PM---Hi
team,]向雅 ---02/13/2008 01:21:30 PM---Hi team,
