[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [gcmd-dev] Re: Internal Viewer Features

From: Micha
Subject: Re: [gcmd-dev] Re: Internal Viewer Features
Date: Fri, 19 May 2006 00:03:42 +0200
User-agent: Alpenglühn 7.2

| The difference between hex and text is not big when we're dealing with 
| ASCII, but once you start searching for text with extended characters 
| (in different languages), each character translates into more than one 
| hex byte.

ok, that's an argument 

| > (btw. marking a hex selection is somehwat tricky by now ;)
| >   
| Please elaborate:

If i try to mark a hex (or binary char) combination, with mouse,
either in hex dump or in binary view, the highlighting starts somewhere 
around but never exactly under the pointer.
It also destroys the displayed chars on screen. 
Can this be triggered by my huge fontsize for my large screen ?
The bookmark titles as shown in in the bookmark manager also 
were always hard to read (even in old gtk1 gcmd) though this was
not crapped in the same way, it just did cut lines vertically.

| Currently, you press "CTRL+F" to find something, and then you can press 
| F3 to repeat the same search again without the search-dialog even 
| appearing (or SHIFT+F3 to search backgrounds).
| If you want to refine your search, you press CTRL+F again, and the 
| search dialog appears (and I will soon make it appear with the previous 
| search text already in the entry-box).

That's exactly the one key i was talking about ;)
The question is, what will happen more often:
That a user refines a search, (or starts looking for another string)
or that you will be satisfied with the first matches.
IMHO the former, but i have no statistical data, of course ;)
it's just my very own behaviour.

Attachment: binaryview.png
Description: PNG image

reply via email to

[Prev in Thread] Current Thread [Next in Thread]