| |
> This code flips between the two buffers for 10 seconds and then makes sure the
> current buffer is set back the Normal:
>
> gettick flipthen
> add flipthen, flipthen, 10000 // ten seconds
> GetDisplayFlags(d)
> LoopIt:
> // SwapDisplayMemory
> xor d, d, DISPLAY_POPUP ; show popup memory
> SetDisplayFlags(d)
> wait 5
> gettick flipnow
> brcmp LT, LoopIt, flipnow, flipthen
>
> // make sure the current display is the normal display
> GetDisplayFlags(d)
> and d, d, ~DISPLAY_POPUP
> SetDisplayFlags(d)
Is it possible to write in the display popup buffer? So that we can do double
buffering? I made some quick tests, but it seems the drawing routines always
write in the normal display buffer...
Julien
|
|
Message has 1 Reply:
 | | Re: What do these macros do?
|
| (...) It is possible to write to the popup buffer but only by using the IOMap routine (SetDisplayPopup). The regular system calls which write to the LCD all write to the normal display memory. Unfortunately, as Dick Swan suggested, the current NXT (...) (18 years ago, 24-Jan-07, to lugnet.robotics.nxt, lugnet.robotics)
|
Message is in Reply To:
| | Re: What do these macros do?
|
| (...) Lots of very cool stuff deleted. Sorry I missed your original message, Jeff. You can write to both the Normal and Popup screen memory and toggle back and forth between which one gets displayed. This code flips between the two buffers for 10 (...) (18 years ago, 16-Jan-07, to lugnet.robotics.nxt, lugnet.robotics)
|
12 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
Active threads in...
NXT programmable brick
Robotics
|
|
|
|
|
|
