LB Booster forum

LB will draw a bmp at the location of the pen, LBB will not. Not sure if this is an intended feature for LB or not, but it caught me out so posting for anyone else. Please see the LB Help manual. You will find it says this: ' print #handle, "drawbmp bmpname x y". This command draws a bitm...

To me it is displayed like this, line by line and letter by letter I ran this: start = time$("ms") for i = 1 to 100 print "The quick brown fox jumps over the lazy dog" next finish = time$("ms") print finish-start wait Here is the output; 186 milliseconds for 4,500 char...

is there a way to speed up this process and that everything is displayed instantly? I don't know of any way to speed up console output, sorry. It is not particularly slow here, this program displays the text 'instantly' when run as a Console Mode executable (Windows 10): PRINT "The quick brown...

This appears to be an issue with issuing the DS, CS and RS switches, they don't seem to be supported in LBB. This is documented in the Compatibility section of the LBB Help manual (item 9: " The syntax for serial port parameters is slightly different... "). I'm unsure whether LBB ignores ...

Tasp wrote: ↑Sun Feb 07, 2021 11:53 am I'm sure I read somewhere (but now cannot find) a way of running an LBB compiled exe and passing a string$ into it?

Doesn't the CommandLine$ special variable do that (in both LB and LBB) ?

No, the indicated line numbers are not helpfull at all since it can happen in any included file If the error happens in an included file, the indicated line number should correspond to the 'include statement itself, so you can then study that file separately (e.g. try to compile it) to discover whe...

The compiler will give you little info (in this example a quote is missing) but that's all. The "11 out of 108 lines processed" should give you some idea where the problem is. If not, a more "verbose" output could be really helpfull ;) LBB was originally designed to 'boost' prog...

Or maybe if I moved maphandle out of the Select Case section and dropped it down the code to just above next You should have done that from the start, I'm surprised that it ever worked the way you had it. I still think that logically you should produce the textbox before deciding what format it sho...

I would expect that in evaluating CASE 10 all other CASE statements would be ignored, but clearly it is not. Likewise, when evaluating CASE 1 to 9, I would expect that CASE 10 was ignored. You are still not seeing it. Unroll the loop so that there is neither a for...next nor a select statement. Wha...

the position of Stylebits is important and MUST come after the related textbox otherwise it relates to the texbox preceding it. Because of your FOR loop, you effectively have code like this: TextBox #main.tb, hPos, (bHt)*i, bWidth+1, bHt+1 Stylebits #main.tb, _ES_LEFT, _WS_BORDER, 0, 0 TextBox #mai...