BritLion's Putchars

[LCD]

Sorry! Perhaps I should have made it clearer. I did show speed test data for block sizes from 1x1 to 8x8 though! I called it putChars because it can put more than one!

I did oversee the "s" in PutChars, so my fault.

Code:

SUB putChars(x as uByte,y as uByte,width as uByte,height as uByte,dataAddress as uInteger)

If you change the first line to read that way, I'm quite certain it would work exactly as you wanted :-) It would call the 3rd variable width, and the fourth one height instead; but they get used by name in the routine.
I'm definitely sticking to data being used in columns before rows, though. It's just faster that way. Ironically, it's faster to paint attributes in rows and then columns.

I know this (Yes, I'm able to change the call order myself), but we want some kind of standard if Boriel will put the routine into includes library, and in all Basic variants I know, width comes before height. I think, standartized calls are not a bad idea.You can still use the complete columns data format, I support this as it gives best compression of data, if the user wants to compress them. And if it is faster, I see no reason why change this. The BorIDE graphics editor will support this format.

This might lead to data being in a format that's more convenient for the computer and less convenient for the human reading it; but that's the way to get speed!

Thats why I definitivly want to add a Graphics editor to BorIDE, which will produce the correct data format for your routine.

I'll see about adding a routine then, that puts attributes on top of the screen data, and either takes one attribute for all of the squares, or assumes it's immediately after the screen data. And actually, since we just had a pointer go through the screen data if we follow on immediately, then we shouldn't need to calculate the attributes address at all - we're already pointing at it.

Great, that was what I wanted. I was meaning not the calculation of attribute address on screen, but the attributes source in the memory, after the bitmap data.