TheBackShed.com

Forum Index : Microcontroller and PC projects : MM+ GUI trouble

Author

Message

kiiid

Guru

Joined: 11/05/2013
Location: United Kingdom
Posts: 671

Posted: 05:32am 21 Oct 2016

Copy link to clipboard

Print this post

I have been trying to figure out some issue with GUI controls. The touch keyboard is very destructive and I need to update the entire screen after it has been used. I know there are GUI interrupts, but they are for the touch interface in general.
How to find out when the touch keyboard has been on the screen and gone, so I can update after it?

http://rittle.org

--------------

Zonker

Guru

Joined: 18/08/2012
Location: United States
Posts: 767

Posted: 04:47pm 21 Oct 2016

Copy link to clipboard

Print this post

Hey Kon..

I'm still kinda of a newbie on GUI stuff, but not sure what you mean... Maybe your screen designs have lots of little pictures, or other elements that get over written, then you would have to reconstruct the screen background...?

Maybe we need a "container" like object that you can fill and it would be controlled through the GUI system, working like the other controls...

The simple stuff that I have strung up so far seems to be well behaved, but not much fancy stuff has been added...

Maybe a screen shot would be in order... Edited by Zonker 2016-10-23

matherp
Guru

Joined: 11/12/2012
Location: United Kingdom
Posts: 10209

Posted: 10:08pm 21 Oct 2016

Copy link to clipboard

Print this post

Quote How to find out when the touch keyboard has been on the screen and gone

You use TOUCH(LASTREF) in the penup interrupt. Unfortunately in 5.2 there is a bug and this returns 0 for the keyboard and numberpad so the workround is to set a flag in the pendown interrupt when TOUCH(REF) is the relevant control and test it in the penup interrupt

isochronic
Guru

Joined: 21/01/2012
Location: Australia
Posts: 689

Posted: 08:29pm 24 Oct 2016

Copy link to clipboard

Print this post

Java-world has things called "layout managers" which can be though of as a container of sorts...their job is to manage the screen refreshes when the screen is updated, modified, redrawn, changed, drawn on similar-but-different screens, etc.
They are quite tricky, and there still has to be the action handling to service the screen widgets contained. A long time ago I wrote a "database form" type that implemented database access through SQL and set up a default vertical array of fields etc, but early java had a lot of bugs and the screen updates would leave old edges still drawn - OK for data but too messy for a product. A lot of work

, but a necessary hassle maybe.

Print this page

To reply to this topic, you need to log in.