Pinboard memory

I have a big backdrop. Very big. With Aemulor loaded, no problem. But when I come back from command line, Pinboard complains it has no memory left to load my sprite again. 19 MB (loaded) + 19 MB (loading) is a bit too much here :)

Not really a bug, but a ‘free before loading’ would probably help here. Or perhaps a ’don’t load me again’, when it’s not necessary (here it’s not: no wimp mode change).

but a ‘free before loading’ would probably help here. Or perhaps a ’don’t load me again’

Converting the sprite to a JPEG might help as well.

Converting the sprite to a JPEG might help as well.

I was under the impression that RISC OS had to convert the JPEG to display it, hence the slower display rendering when using a JPEG

I was under the impression that RISC OS had to convert the JPEG to display it, hence the slower display rendering when using a JPEG

Possibly, but I actually never noticed any difference.

I was under the impression that RISC OS had to convert the JPEG to display it, hence the slower display rendering when using a JPEG

But this has been described as a memory problem, so its reduced size may help.

JPEG rendering is much faster than it was in the olden days!

Possibly, but I actually never noticed any difference.

Sounds like the slower rendering in RO4.02 was something you missed out on¹, however the rendering speed wasn’t the specific item I was thinking of -

But this has been described as a memory problem, so its reduced size may help.

I was referencing the conversion – to a format that occupies more space than JPEG as I don’t think the system renders the JPEG direct (if I’m wrong it isn’t an issue)

¹ JPEG use was interesting/useful but without an SA machine it was painfully slow to move windows across the display.

JPEG use was interesting/useful but without an SA machine it was painfully slow to move windows across the display.

But that really was the olden days!

But that really was the olden days!

I am but a spring chicken.

The point being that the original posting contains the heart of the issue – the image is being reloaded and reloading and converting won’t help, but detecting the same image being selected would help. F5 screen refresh ought to sort any instances of image update with same filename.

But that really was the olden days!

It’s still noticeably slower.

detecting the same image being selected would help

Probably :)

I have a big backdrop. Very big.

Tu fais le faraud! Tu te vantes!

:-) I do like idiomatic expressions!