wxHexEditor: wx-based Hex Editor!
Re: colored text - I'd have it off by default, anyway, I'm sure. I'm probably too old-fashioned to stare at code or binary/hex file contents in anything but black and white.
[ Puppy 4.3.1 JP, Frugal install ] * [ XenialPup 7.5, Frugal install ] * [XenialPup 64 7.5, Frugal install] * [ 4GB RAM | 512MB swap ]
In memory of our beloved American Eskimo puppy (1995-2010) and black Lab puppy (1997-2011).
In memory of our beloved American Eskimo puppy (1995-2010) and black Lab puppy (1997-2011).
I don't know if changing null character is good thing.
I don't know actually but don't think if it's normal to have null at copied text. Better to keep current structure. At least for now... C++ might allow null on strings but I have doubts if gnome-clipboard supports it at text target...
@Disciple, I am developing on OpenSUSE 11.4.
That error might be about different gcc version.
I don't have such problems on gcc 4.5.1...
Are you using 4.6 ?
In this time I make some improvements to revision 226:
I am gonna add a file checksum before giving a new release...
I don't know actually but don't think if it's normal to have null at copied text. Better to keep current structure. At least for now... C++ might allow null on strings but I have doubts if gnome-clipboard supports it at text target...
@Disciple, I am developing on OpenSUSE 11.4.
That error might be about different gcc version.
I don't have such problems on gcc 4.5.1...
Are you using 4.6 ?
In this time I make some improvements to revision 226:
So you don't needed to change/adjust your disk permissions by hand...| erdem_ua
Added file owner change for non-windows OSes if permissions are not enough.
Added missing block indication to file comparison function.
Fixed Compare Dialog error on Win by using bigger stack.
Improved Dissassembly. Now decompiles selected block up to 100 bytes.
Fixed broken menus on OpenRecent menu repair.
Fixed Invisible SearchPanel and ComparePanel contents on File changes.
Fixed OpenRecent not working bug.
I am gonna add a file checksum before giving a new release...
Well, I meant more along the lines of letting the user choose from the warning dialog whether or not they'd want to go ahead and have it converted to a form that other programs (or the system clipboards) might not have a problem with.
If they read the warning, they'll know (hopefully) that attempting to copy either way into another hex-editing session isn't a good thing, so... hopefully, they'd be aware they should only do it if they're going to do something like copy-paste it to notes in a text file. (You don't want to see my handwritten notes... honest. )
If they read the warning, they'll know (hopefully) that attempting to copy either way into another hex-editing session isn't a good thing, so... hopefully, they'd be aware they should only do it if they're going to do something like copy-paste it to notes in a text file. (You don't want to see my handwritten notes... honest. )
[ Puppy 4.3.1 JP, Frugal install ] * [ XenialPup 7.5, Frugal install ] * [XenialPup 64 7.5, Frugal install] * [ 4GB RAM | 512MB swap ]
In memory of our beloved American Eskimo puppy (1995-2010) and black Lab puppy (1997-2011).
In memory of our beloved American Eskimo puppy (1995-2010) and black Lab puppy (1997-2011).
I have this error in my old version of Puppy, which uses gcc 4.2.2, and also in Arch Linux with gcc 4.6.eua wrote:@Disciple, I am developing on OpenSUSE 11.4.
That error might be about different gcc version.
I don't have such problems on gcc 4.5.1...
Are you using 4.6 ?
I'm only using the makefile. Maybe there's an option you're using in codeblocks which affects it.
Do you know a good gtkdialog program? Please post a link here
Classic Puppy quotes
ROOT FOREVER
GTK2 FOREVER
Classic Puppy quotes
ROOT FOREVER
GTK2 FOREVER
Hmmm. I tried building it in codeblocks and it failed the same way.
Do you know a good gtkdialog program? Please post a link here
Classic Puppy quotes
ROOT FOREVER
GTK2 FOREVER
Classic Puppy quotes
ROOT FOREVER
GTK2 FOREVER
That error looks weird because cannot see an error over there.
It probably related with Unicode build... But I use unicode build also.
Weird.
Since I don't have same error. I couldn't help about it.
It probably related with Unicode build... But I use unicode build also.
Weird.
Since I don't have same error. I couldn't help about it.
Now need a give release after bug fixing season...on svn trunk, File checksum calculation implemented via adding hashlib++
I found why you got error.
this while tigers error.. But I don't know how can I count UTF8 length without it.
This function founds "real" length in bytes instead of character count...
Since that length is not equal with target.Len(), we needed to do that.
Will look what I can to remove that error.
Edit: Fixed on latest svn trunk. Please check...
Code: Select all
wxCharBuffer a = target.ToUTF8(); //Convert to UTF8 Binary
int i=0;
while(a[i++] not_eq 0); //Find stream size
This function founds "real" length in bytes instead of character count...
Since that length is not equal with target.Len(), we needed to do that.
Will look what I can to remove that error.
Edit: Fixed on latest svn trunk. Please check...
Released wxHexEditor v0.11 Beta
You can grab new version v0.11 Beta from http://wxhexeditor.sf.net
Oops - I keep forgetting to say thanks for the new .pet (and the new version). I installed it right away (in June), but haven't actually gotten around to testing it.
[ Puppy 4.3.1 JP, Frugal install ] * [ XenialPup 7.5, Frugal install ] * [XenialPup 64 7.5, Frugal install] * [ 4GB RAM | 512MB swap ]
In memory of our beloved American Eskimo puppy (1995-2010) and black Lab puppy (1997-2011).
In memory of our beloved American Eskimo puppy (1995-2010) and black Lab puppy (1997-2011).