changing displays example needed

SynapticBytes

I'm trying to re-organise the displays as I want several pixel displays and several text displays, but I am having no end of trouble figuring out the syntax and getting it to work.

The cheatsheet says to "assign" the display mode to the display, so is that a literal assignment, using "+"? Which is correct

displayMode(0).mode = displayMode.text or
displayMode(0).mode displayMode.text

I've tried multiple variations and they are all giving me grief, as when I try to use the changed displays, the methods I'm using give me errors saying they are not in the map. I've tried printing out the maps to see what they are set to, but I either get what looks like the default map one way, or something corrupted showing bits of my program code intermingled with the map functions.

So if I could just a clear example with a basic test to see it work, that'd be great. Thanks.

edit

So assigning to unallocated displays sort of works, such as this
display(2).mode = displayMode.pixel traceDisplay = display(2)

Doing that, my method is at least being called, however it doesn't seem to be displayed. I know it's working, as when I restart the game, it shows all the lines I've been drawing on this display, before my initial clear, but while the game is running, it doesn't display the lines as they are being drawn. Display 2 is my highest (priority, lowest number) display.

As for the assignment,a s I said it seems to work on an unassigned display, but when I try to re-organise and change the default displays (i want text on display 0, sprites on 3, and pixel on 4 and 5) it becomes a mess of errors.

Russell.

SynapticBytes

So I thought I'd try some sample code. I wanted to re-organise all the displays except the default gfx and text. So I expected the following code to run and show me two coloured lines in an X, two lines of text in different positions, two sprites and my "start" and "end" debug statements.

Unfortunately, all I get is a blank screen, and not even the default cursor when the program ends. I have to enter "clear" to get the cursor back. I'm obviously missing something here.

`clear
//display test
print "start"
display(6).mode = displayMode.pixel
p6 = display(6)
display(4).mode = displayMode.pixel
p4 = display(4)
display(3).mode = displayMode.sprite
s3 = display(3)
display(2).mode = displayMode.text
t2 = display(2)
display(1).mode = displayMode.sprite
s1 = display(1)
display(0).mode = displayMode.text
t0 = display(0)

//text
t0.clear
t0.row = 1
t0.print "Display 0"
t2.clear
t2.row = 25
t2.print "Display 2"
//pixel
p6.line 0,0,100,100,color.red, 10
p4.line 0,100,100,0,color.aqua, 10
//sprite
sprite1 = new Sprite
sprite3 = new Sprite
sprite1.image = file.loadImage("qixotic/player.png")
sprite3.image = file.loadImage("qixotic/pinkie.png")
s1.sprites.push sprite1
s3.sprites.push sprite3
sprite1.x = 50
sprite1.y = 100
sprite3.x = 50
sprite3.y = 25

print "end"
'

edit

Hmm, sidenote, why is the code not being formatted here as well?

SynapticBytes

OK, so I figured out the problem. Pixel displays do not have their background initialised to clear. I assumed they would. Is there some reason clear isn't the default? The cheat sheet advertises the layering ability of the displays, so I think that implies they start clear.

My other problem was the fact I was changing display(3), which is the display also used for the command line, which is why I wasn't getting my cursor back. So that makes it a bit of a gotcha that if it is left as an available display to program, it then messes up the command line when finished.

SynapticBytes

And the final piece in my little puzzle I believe.

Does the "clear" command reset all the display modes back to their defaults? I was using it as an easy way to wipe the screen across all displays, but it looks like it's doing more than just clearing the display, which I think is back to my original problem of why I was getting method errors because I was trying to access functions on a display mode that had been reset to default?

Russell.

jstrout

Well, it seems you figured it all out before I could jump in to help.

Yes, the clear command (the code of which, by the way, is available to you in /sys/startup.ms) not only clears but also resets all displays. The point of it is to get you back to a standard, legible state, particularly since (as you noticed) you might otherwise be in a state where you can't see your typing.

There are several good examples of setting up layered displays in the /sys/demo directory. The drumMachine, flappyBat, forestFire, levelEditor, mochiBounce, platformer, and many others all do it. But I can understand your confusion, particularly given the current thin docs.

Pixel displays clear to black by default. I'm not convinced that clearing to clear is any more intuitive than black — but maybe. I will think about it (and thank you for the suggestion!).

jstrout

Well, it seems you figured it all out before I could jump in to help.

Pixel displays clear to black by default. I'm not convinced that clearing to clear is any more intuitive than black — but maybe. I will think about it (and thank you for the suggestion!).