Re: [cdt-debug-dev] RetargetAddMemoryAction

[John Cortell <john.cortell@xxxxxxxxxxxxx>]

Samantha, never mind. I was confused. IAddMemoryBlocksTarget is not 
necessarily, and probably wouldn't be, implemented by a model object.

John


At 02:47 PM 5/24/2006, Samantha Chan wrote:
> Hi John -
>
> Correct.  MemoryViewUtil#isValidContext asks if the model is terminated /
> disconnected.  Communication to the model should be performed on a
> background thread.  Therefore, I needed to schedule a job to do it.
>
> Thanks...
> Samantha
>
>
>
>
>              John Cortell
>              <john.cortell@fre
>              escale.com>                                                To
>              Sent by:                  CDT Debug developers list
>              cdt-debug-dev-bou         <cdt-debug-dev@xxxxxxxxxxx>
>              nces@xxxxxxxxxxx                                           cc
>
>                                                                    Subject
>              05/24/2006 03:33          [cdt-debug-dev]
>              PM                        RetargetAddMemoryAction
>
>
>              Please respond to
>                  CDT Debug
>               developers list
>              <cdt-debug-dev@ec
>                 lipse.org>
>
>
>
>
>
>
> Samantha,
>
> In RetargetAddMemoryAction.updateAction(), the setEnabled() method is
> called directly (or not at all), whereas in the parent class
> implementation (AddMemryBlockAction.updateAction) the same operation
> is carried out in a Job. I was wondering why. Does it have something
> to do with the fact that the latter case needs to call
> MemroyViewUtil.isValidContext(), but the former doesn't?
>
> John
>
> _______________________________________________
> cdt-debug-dev mailing list
> cdt-debug-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev
>
>
> _______________________________________________
> cdt-debug-dev mailing list
> cdt-debug-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev