It is convenient to use this tool from commands line, but it's not available in PATH by default. Installer can change this.
Indeed I could bundle this program with toolbar installers.
Some companies offers me $1 for each installation. I can prepare an installer but not like them. I love one executable programs. Even in old days while using windows.
I think it's easy to install it to windows path. But I want to continue one Executable approach for a while instead of installers.
Ok. Why not to add a dialog that will popup if wxHexEditor can not find itseld in the %PATH%?
Well. This is good question. But how many developer want to have wxHexEditor at their default PATH? Indeed executing it from developer tool directory looks better. Or from it's shortcut at desktop. Auto-Popup for wxHexEditor will disturb users.
I could add "Install" item to "Help menu" for windows. Also could create shortcut at Windows Start menu might work. It's easy to do at XP, but don't know if it's true for Vista/7/8 due it might require root rights.
But using default path for wxHexEditor installation makes me thinking. It's looks like a virus behaviour to me, not proper, and there is optional language files of wxHexEditor. So using "Program Files" is better for installation of wxHexEditor at Windows... Might possible to do it later.
Adding wxHexEditor to path is another problem. Firstly, I don't know if any hex editor make it. We could ask users for adding wxHexEditor path to default %PATH% variable. Or could windows start wxHexEditor from it's shortcut available at %PATH% directory? It's a better option.