Bomb Bloke, on 25 June 2016 - 02:38 AM, said:
Just reading the code, both blocks look ok to me, though A will miss any monitors directly touching the computer (any particular reason you're avoiding peripheral.getNames()?), whereas B should get all monitors of the correct size.
The difference in detection (all vs. only remote) is intentional actually. The program this is written to supplement only sees 'remote' monitors and I've never bothered to remove that limitation, so I kept that limitation in code block A which I've ended up using for now.
I only have one reason for not using peripheral.getNames() - as dumb as it may make me seem, I wasn't even aware of it. Thanks for pointing it out.
Bomb Bloke, on 25 June 2016 - 02:38 AM, said:
What I don't get is why you're bothering to set the scale to 1. Why not just set it directly to 3, and then measure the dimensions?
Point taken

I was under the impression that changing textScale helped avoid some of the issues I have apparently run in to (from previous AaP threads). I'll make the suggested change and see how that works.
Bomb Bloke, on 25 June 2016 - 02:38 AM, said:
Dog, on 24 June 2016 - 09:16 PM, said:
Trying to edit the OP just makes a mess of it
What sort of mess?
If it removes all the line breaks, that's been happening for me too, though I'm not sure why. I've found that avoiding the quick editor and going directly to the full post editor (middle-click the "edit" link) works around it.
For me it was not respecting my code indentation and left justifying all the code. Now that I think about it, I could have just re-pasted the code back in after editing - apologies that it didn't occur to me when I double-posted. I wasn't aware of the middle click feature - thanks for that...very handy
EDIT: I finally figured out what's going on - thanks to BombBloke for making me re-examine my approach to detecting peripherals and monitor sizes. This program supplements another program that also uses a similar detection routine that sets the textScale to 1 on all monitors detected (to determine their size) and clears them before setting their individual textScales. When this program called the other program all the monitors would be set to textScale 1 and be cleared; thus defeating my attempts to set the textScale and put text on the monitors. This occured to me when I set the monitors to textScale 2.5 and they were detected, but only displayed text at textScale 1, and only after the timer started. Bottom line - it was my fault, not a bug or problem in ComputerCraft - I was thinking in a vacuum and not considering the program this one was calling.
Edited by Dog, 25 June 2016 - 04:17 AM.