kaitai_ide_vscode icon indicating copy to clipboard operation
kaitai_ide_vscode copied to clipboard

None of the commands work

Open Moneyl opened this issue 5 years ago • 4 comments

Using windows 10. The kaitai struct compiler and visualizer were already installed on my system when I installed the vscode extension if that matters. Tried running "compile to target language", "compile and examine ksy", and "open file as hex". None of them work. They all give "command not found" errors.

Code_tM7ev07x6H Code_JH9JYfjUbx Code_IYYuExwj9U

Moneyl avatar Feb 15 '20 18:02 Moneyl

I should add that this happens regardless of the file used and also that the KsExplorer panel is empty.

Moneyl avatar Feb 15 '20 18:02 Moneyl

Hello! I sincerely apologize for the late response. Being so new to github issues, I got so into fixing the issue that I forgot to report back to say it should be fixed.

The Cause of this Issue: In previous versions, it seems that I only had the extension itself activate when the hex editor was opened.

In one of the versions that followed, this should now be fixed.

Notes:

believe it or not, this extension actually doesn't require the kaitai struct compiler itself or the visualizer installed due to using its own version of the KSC that was compiled to javascript and embedded within the extension. Therefor, it should run without any issues due to them missing.


I'll leave this issue open for another week or two just to be sure this is resolved. If there's not response by then I'll assume this issue has been resolved.

Thanks for the report!

fudgepop01 avatar Jun 27 '20 16:06 fudgepop01

Hi,

for me neither one of the commands work, when executing from the menu. Nothing seems to happen and I can not found any error log / messages.

Using VsCode 1.76 on Windows 11.

Regards Hendrik

lhendrik avatar Mar 08 '23 11:03 lhendrik

Hello! I have figured out the cause of the commands failing to work altogether without a error message. There was a line of code checking to see if something was a string when it should have been checking to see if it was a boolean, if anything.

I have updated the extension with improvements to the hex viewer. I hope this helps!

fudgepop01 avatar Apr 25 '23 21:04 fudgepop01