Forum Replies Created
I received an email from the UltraEdit support people today. It turns out this is a known bug in version 12: When you hex view, UE shows you the internal representation of the file, which is always UTF-16, and not what the file itself contains.
This is fixed in UltraEdit 13.
Thanks for your attention,
I used UltraEdit 12.20a to view the files. And, never mind. The problem is UltraEdit.
Well, I have a version of the autocomplete plugin that check configurations correctly. It looks for the EVENT_FILE_OPENED and EVENT_DOC_SEL_CHANGED events and then calls QueryConfig.
This isn’t the correct fix, though, it’s a crude hack. The right way to fix this is to have the editor send the EVENT_CONFIG_CHANGED notification as it is advertised to do.
I will upgrade and try it again.
Thanks for the update.
I just downloaded the new source, compiled it with VS2005 and installed the plugin. When I start the editor the plugin crashes on an assertion failure at etlframe.h line 331.
I have emedit version 5.0, so I think this is not supposed to happen. What do I need to fix?