[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-debug-dev] RetargetAddMemoryAction (3.2)
|
John,
Please enter a bugzilla report about this problem.
The specification if IAddMemoryBlocksTarget#addMemoryBlocks indicates that
client should query for default renderings and create them. There is no
option to not to create them. So, this is sort of working as designed,
that your implementation must query for default renderings and create them
when called.
However, you are correct that the interface does not give you enough
information to duplicate the platform's behavior. We probably need some
extension to the existing interface to give client more information on
where they are being called from or why they are being called.
Thanks...
Samantha
John Cortell
<john.cortell@fre
escale.com> To
Sent by: platform-debug-dev@xxxxxxxxxxx
platform-debug-de cc
v-bounces@eclipse
.org Subject
[platform-debug-dev]
RetargetAddMemoryAction (3.2)
05/25/2006 07:17
PM
Please respond to
"Eclipse Platform
Debug component
developers list."
<platform-debug-d
ev@xxxxxxxxxxx>
Samantha,
It appears RetargetAddMemoryAction fails to forward
the 'addDefaultRenderings' option to the IAddMemoryBlocksTarget. As
such, the add-blocks delegate must either assume one or the other in
all cases. Unless I'm mistaken, this will not allow for the platform
behavior where a monitor added via the "+" toolbar item will add the
default renderings but a monitor added via the "Add Memory Rendering"
dialog won't.
If you can confirm this, I'll enter a bugzilla report.
John
_______________________________________________
platform-debug-dev mailing list
platform-debug-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-debug-dev
