My "Edit with HHD HEX Editor Neo" right-click entry is doing bugger-all when running in Directory Opus. All other entries are working as they should.
Am guessing that the program in mention has added itself in some non-standard way, but I have not got a clue as to where I should start looking.
Any ideas greatly appreciated.
I've investigated this and the HDD Hex Editor Neo context menu extension is passing an invalid parameter which causes Opus to cancel the action.
However, I also checked what Explorer does when given the same invalid parameter and it seems Explorer ignores it. Opus should probably do the same for compatibility.
I've spoken to GPSoftware about this and a change to make Opus allow it through should be included in the next release (presumably numbered 9.1.0.7).
In the mean time you can create a context menu item which does work by making one which runs this command:
"C:\Program Files\HHD Software\Hex Editor Neo\HexFrame.exe" "%1"Technical details, for anyone interested: Their context menu is calling IDataObject::GetData with a FORMATETC::lindex of 0 (zero) which is invalid (as I understand things, anyway) for the type of data they are requesting (DROPFILES).
[quote="MSDN"]Return Values
...
DV_E_LINDEX
Invalid value for lindex; currently, only -1 is supported.[/quote]
Excellent, thank you very much for the info.
Thanks for mentioning Hex Editor Neo, by the way. It looks excellent and I hadn't come across it before. I may buy the Pro version next time I'm dealing with binary file parsing as, with the structure viewer, it looks like exactly what I wished I had the last time I was doing that kind of work.
Yes, the HHD editor takes the prize as far as I am concerned, and does not have any of the drawbacks that are so often seen in similar products.
I work for HHD Software.
Just found this topic through Google. Thank you very much for providing detailed information about a bug in our software. leo, you are right, the parameter submitted to GetData method is incorrect. We'll fix a bug and release an update in a couple of days.
Thank you very much again for information and kind words about our product!
Thanks for letting us know. It's nice to see a product that gets quick updates!
An update to Opus which makes it tolerant of lindex=0 will be out soon as well. There is at least one other context menu extension which does the same thing and the IDataObject documentation is pretty ambiguous so I bet there are more out there. Explorer allows it so it makes sense for Opus to do the same. I've got a beta version of Opus with the change and the Hex Editor Neo context menu works fine with it.
(Of course, it still makes sense to change Hex Editor Neo, even though Opus won't mind soon, in case another file manager is strict about the value.)
The update to Hex Editor Neo which fixes the problem has been released. I just ran the program to look at something else and the update check found it.