Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[dsdp-dd-dev] RE: [platform-debug-dev] AbstractTableRendering -mixed HEX/ASCII

Currently in the Memory View, when the two separate renderings are
displayed side-by-side, the cursor and scrolling are kept in sync.  When
you change the selection from one rendering, the cursor from another
rendering will follow.  When you scroll in one rendering, the other will
follow as well.  You also have the option to break the synchronization.

Depending on how your renderings are set up, your debugger also has the
option to create a default set of renderings when a memory block is
created.  For example, you can define to have both HEX and ASCII renderings
created by default when your memory block is created.

The only drawback with this approach is that you get dual scroll bars and
two address columns.  (But user can hide the address column from the
rendering.)  However, it gives flexibility as the user can scroll the
renderings independently.  It also allows user to look at different
combinations of renderings at the same time.

I would not recommend using AbstractTableRendering as the base
implementation to combine two renderings.  You will need to create you own
rendering if you want to combine the two.  This is because the content
provider of the rendering depends on the number of columns in the table to
calculate how much memory is needed from the model.  Combining the two
renderings will change the number of columns in a table and hence breaks
the content provider.

Please try opening the second Memory Rendering Pane and look at two
renderings side by side that way.  If you still have issues with this,
please let me know and I would try to address them.


             "Williams, Ted"                                               
   >                                                To 
             Sent by:                  "Device Debugging developer         
             platform-debug-de         discussions"                        
             v-bounces@eclipse         <dsdp-dd-dev@xxxxxxxxxxx>, "Eclipse 
             .org                      Platform Debug component developers 
             01/12/2006 02:16                                           cc 
                                       RE: [dsdp-dd-dev] RE:               
             Please respond to         [platform-debug-dev]                
             "Eclipse Platform         AbstractTableRendering  -mixed      
              Debug component          HEX/ASCII                           
             developers list."                                             

When I'm looking at ASCII, mixed mode allows me to quickly see that a
whitespace character is 0x20 or 0x0D, without opening a second
"rendering". It's convenient that the two stay in sync and in many
modern debuggers, a selection on one side causes a corresponding
selection in the other. I'm sure there are alternative solutions, such
as using tooltips/datatips, but as a user, I prefer the side by side

Would you recommend using AbstractTableRendering as a base for such an

Do any other clients anticipate side by side hex and ascii renderings?


-----Original Message-----
From: dsdp-dd-dev-bounces@xxxxxxxxxxx
[mailto:dsdp-dd-dev-bounces@xxxxxxxxxxx] On Behalf Of Samantha Chan
Sent: Thursday, January 12, 2006 10:23 AM
To: Eclipse Platform Debug component developers list.;
Subject: [dsdp-dd-dev] RE: [platform-debug-dev] AbstractTableRendering
-mixed HEX/ASCII

Looks like you are trying to put two renderings into one.  The vertical
scrollbars are provided by the table viewer.  I don't think there is a
way of getting rid of them.  I am not familiar with ScrolledComposite,
but the table viewer also has its own horizontal scrollbar.  I suspect
that with this approach, you will always end up getting dual horizontal
and vertical scroll bars.

To achieve having  mixed HEX and ASCII in one rendering, I believe you
will have to create your own rendering using a single table.

When I said we displayed two renderings side by side, I actually meant
that we have the two renderings in separate memory rendering container.
(The second rendering pane of the Memory View is opened.)  The
renderings are completely independent of each other and have their own
scroll bars and address columns.  Have you tried using this approach?
Why do need to host two "renderings" in a single rendering?

platform-debug-dev mailing list

Back to the top