FineLineIDE

[timmers]

Full tabs compatibility option has been added to the next version of FL!

Norm

Cool.

Is there a way to disable "code crosses boundary" prompts?

I will come back to the UP programmer settings. Does FL just add the switches as typed or are they decoded/fiddled with at all?

[Normnet]

Cool.

Is there a way to disable "code crosses boundary" prompts?

I will come back to the UP programmer settings. Does FL just add the switches as typed or are they decoded/fiddled with at all?

That would be a function of the compiler (PBP) not the editor (FL).
Unless it's a '<FL_xxxxx>' comment command all switches are for the compiler.


Norm

[mister_e]

NAH, easy solution when using MPASM, add the following line at the top of your code.

@     ERRORLEVEL -306 ; supress code boundary message

It is just a warning, I guess the function in MCSP just ignore it when it happen. So yeah, it could be a feature of FineLine. Just parse the begining of the message, analyze it, ignore it... and you're done

[Normnet]

NAH, easy solution when using MPASM, add the following line at the top of your code.

@     ERRORLEVEL -306 ; supress code boundary message

It is just a warning, I guess the function in MCSP just ignore it when it happen. So yeah, it could be a feature of FineLine. Just parse the begining of the message, analyze it, ignore it... and you're done

On compile button press the IDE saves your code to it's file and passes the file path to PBP.exe to compile to an assembly file.
As a rule the IDE doesn't fiddle with the code as it wouldn't reopen the same if the IDE was closed after a compile.
Thinking out loud I suppose the IDE on compile could add the line "@ ERRORLEVEL -306 ; suppress code boundary message" to file to be compiled and re save the original after compile is complete but their really is no reason to do so.
Another way would be if FL were to simply not report a specific compiler warning however again no reason to do so as adding Mr E's line of code is the intended method.

Norm