[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
RE: [platform-debug-dev] [Memory View]: Changing selection inVariables view affects the content of Memory view
|
Hi
The rendering view pane organizes memory blocks based on
IMemoryBlockRetrievals. It will display memory blocks for the selected
memory block retrieval. The reason why the view goes blank is probably
because you have separated your memory block from your debug target. i.e.
when #getAdapter(IMemoryBlockRetrieval.class) is called, you return an
IMemoryBlockRetrieval object. However, your variables are not returning
any IMemoryBlockRetrieval object when
#getAdapter(IMemoryBlockRetrieval.class) is called. As a result, the view
uses its debug target as its memory block retrieval and cannot find memory
blocks associated with your variables.
To get around the problem, make sure all your debug elements are returning
the same IMemoryBlockRetrieval when
#getAdapter(IMemoryBlockRetrieval.class) is called.
Thanks...
Samantha
"Alexiev, Dobrin"
<dalexiev@xxxxxx>
Sent by: To
platform-debug-de "Eclipse Platform Debug component
v-bounces@eclipse developers list."
.org <platform-debug-dev@xxxxxxxxxxx>
cc
06/17/2005 01:47 Subject
PM RE: [platform-debug-dev] [Memory
View]: Changing selection
inVariables view affects the
Please respond to content of Memory view
"Eclipse Platform
Debug component
developers list."
Sorry if I don't fully understand the design.
I've just played with the new memory window for an hour, but I see
something that I can't quite understand.
As a user experience when the user clicks in a variable in the Variable
View she/he doesn't expect the Memory View to gets blank.
The user doesn't do any operation that results in change of context on
the target.
I am missing something important?
Thanks
Dobrin
-----Original Message-----
From: platform-debug-dev-bounces@xxxxxxxxxxx
[mailto:platform-debug-dev-bounces@xxxxxxxxxxx] On Behalf Of Samantha
Chan
Sent: Friday, June 17, 2005 1:40 PM
To: Eclipse Platform Debug component developers list.
Subject: Re: [platform-debug-dev] [Memory View]: Changing selection
inVariables view affects the content of Memory view
Hi -
Yes, it is working as expected. The Memory View listens for selection
events form the workbench and will try to bring up memory blocks from an
IDebugElement. The idea is that any view may be displaying an
IDebugElement that is capable of retrieving a IMemoryBlock. The view
will
try to find memory blocks associated with the selected debug element and
display them.
Thanks...
Samantha
"Mikhail
Khodjaiants"
<mikhailk@xxxxxxx
To
> <platform-debug-dev@xxxxxxxxxxx>
Sent by:
cc
platform-debug-de
v-bounces@eclipse
Subject
.org [platform-debug-dev] [Memory
View]:
Changing selection in Variables
view affects the content of
Memory
06/17/2005 12:05 view
PM
Please respond to
"Eclipse Platform
Debug component
developers list."
Hi,
RenderingViewPane doesn't filter selection changes from the Variables
view.
Actually, the same applies to the selection changes from any workbench
part, but only those who's elements extend IDebugElement affect the
Memory
view's content.
Is this an expected behaviour?
Thanks,
Mikhail Khodjaiants
QNX Software Systems_______________________________________________
platform-debug-dev mailing list
platform-debug-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-debug-dev
_______________________________________________
platform-debug-dev mailing list
platform-debug-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-debug-dev
_______________________________________________
platform-debug-dev mailing list
platform-debug-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-debug-dev