Feature: Marking and labeling errors in code.

[TheStruggleForAntiSpaghetti]

The Z80asm in SublimeText shows where errors are in the code, and an explanation of what's wrong with each. Also, in the code navigator at the right, each error is marked as such:

This feature is very handy. Would it be possible to have something like that in Klive?

[Dotneteer]

I'm planning a similar functionality; it is already in my backlog. Before that, I want to create a common infrastructure to integrate external Z80 Assemblers, such as SjasmPlus.

[TheStruggleForAntiSpaghetti]

In the meantime, when there's a compile error, the text in the message-box

Code compilation failed, no program to inject.

does not make clear what the issue actually is. A clearer message like

Compile error: check the Output panel for details

would be more apt.

As an extra, it would be useful if the Output panel is not visible to have an optional button in the dialogue box to open it, next to the Ok button.

[Dotneteer]

Sure, this is a good suggestion!

[Dotneteer]

I have changed the messages according to your suggestion. The Output window gets displayed if it is hidden. Soon, I will release the private build with this update.

[TheStruggleForAntiSpaghetti]

When the next build becomes available, I'll test and let you know in this issue thread.

[Dotneteer]

@TheStruggleForAntiSpaghetti, @Pete-L-72, You can download the private build (v0.49.0) from this link: https://1drv.ms/f/c/79da757d3d2b5baa/QqpbKz19ddoggHlnPAkAAAAAyMaLSBXRXrYANw

This release implements the first (rudimentary) version of Klive's background compilation. When the View | Editor | Allow Background Compile option is turned on, this feature continuously runs background compilation and displays errors.

[Pete-L-72]

Downloaded. Probably not coding today tho'.

[Pete-L-72]

I did load it up for a very brief spin. Very initial feedback would be that there should be either a timeout, after which the error is displayed, or maybe the error shouldn't display until focus moves off the line being edited.
Is it recompiling everything from scratch every time you type something? Hmm, maybe it depends what's being typed. I started a line with "l" for ld and it quickly told me I can't start a line with "l" - but if I entered "jp invalidlabel" it took as long as the whole project would take to compile before it told me that invalidlabel wasn't a valid label.

Edited to add: if it background compiles and doesn't find any errors it would be nice if running the project didn't go off and recompile everything. I haven't raised this before but sometimes I don't want to edit the code but want to run it again without changes and it's a little frustrating that it recompiles every time regardless of my not making any edits.