[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-debug-dev] where to start my thread?
|
You need UI components (an action, or something else) to initiate your
non-UI activity.
----- Original Message -----
From: "Yan Chen" <ychen5@xxxxxxxxxxxx>
To: <cdt-debug-dev@xxxxxxxxxxx>
Sent: Friday, April 16, 2004 7:09 PM
Subject: Re: [cdt-debug-dev] where to start my thread?
> Hi,Mikhail Khodjaiants,thank you for helping me.
>
> On Fri, 2004-04-16 at 09:07, Mikhail Khodjaiants wrote:
> > You shouldn't add code to the existing plugins. Instead you should
create
> > your own plugin and implement IDebugEventSetListener. Based on the
events
> > that the debug framework sends you can start your thread, and do
whatever
> > you want to do. That's a standard approach.
> >
>
> I did what you said, create a new non-UIPlugin extends the Plugin class
> and also implement the IDebugEventSetListener, and register the listener
> to DebugPlugin at the startup method of my non-UIPlugin.
> DebugPlugin.getDefault().addDebugEventListener( this );
>
>
> but when I run my runtime-work bench, my new non-UIPlugin never loaded
> by eclipse, So what should I do in order to ask eclipse to load my
> non-UIPlugin before the load of the DebugPlugin.
>
> Thanks!!
>
> Yan
>
>
>
> _______________________________________________
> cdt-debug-dev mailing list
> cdt-debug-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/cdt-debug-dev
>
