Hi again,
Didn't get back to you yesterday because I'm in France and it
was getting late...
Yes, now it works! I had foolishly passed the progress monitor to
the runnable's constructor as well as the run method.
I suppose I was expecting it to be complicated, but with a few
lines of code it all works - it's magic!
Thanks for your help and have a good day,
Antony
On 27/03/2013 18:57, Chris Recoskie wrote:
You should just change the
type of the existing runnable you had.
===========================
Chris Recoskie
Team Lead, IBM CDT and RDT
IBM Toronto
Antony Burton ---03/27/2013
01:03:48 PM---Thanks Chris for the swift reply. I tried
changing my runnable (the one defined as the operation cla
From: Antony Burton
<aburton@xxxxxxxxxxx>
To: "CDT General developers list."
<cdt-dev@xxxxxxxxxxx>
Date: 03/27/2013 01:03 PM
Subject: Re: [cdt-dev] ProgressMonitor in
MBS Custom Pages
Sent by: cdt-dev-bounces@xxxxxxxxxxx
Thanks Chris for the swift reply.
I tried changing my runnable (the one defined as the operation
class in plugin.xml when extending
org.eclipse.cdt.managedbuilder.ui.newWizardPages) to:
public class AIMWizardPageRunnable implements
IRunnableWithProgress {
and in the run method added:
public void run(IProgressMonitor monitor) {
...but when I launch the C Project wizard I get the error:
Plug-in "addProject" was unable to instantiate class
"addProjectRunnables.AIMWizardPageRunnable".
I suppose I must tell the MBSCustomPageManager I have an
alternative runnable, but how?
By the way I am using Indigo and CDT 8.02
Thanks again...
On 27/03/2013 17:03, Chris Recoskie wrote:
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
|