This is actually a very cool way of doing things. Now that I think about it
again, it's almost like the button on the keyboard is mapped in as a button
in your application. You basically replace the LCD (or whatever)
representation of a button with a physical representation of a button, but
the so
Popup windows are always modal-- they are created in a new 'layer' so you can
only access the widgets in the popup. Normal dialogs (without the ATCURSOR
positioning) are usually modal, but there's a hack so that toolbars are still
usable if the dialog accepts keyboard input. This is so virtual key
Create a button widget, and set the PG_WP_HOTKEY property to the PGKEY value of
the key you want to catch. The button will catch that key and send a
PG_WE_ACTIVATE event when it does. If you don't want it to be visible, set the
button's PG_WP_SIZE property to zero.
This is already used by the Pic
To update a transparent label correctly, PicoGUI has to redraw the container
behind it. The label widget sets a flag in the conainer indicating that it must
be redrawn, but if you run pgSubUpdate on the label it never sees this flag in
the container. Running pgSubUpdate on the container will solve
Hi everyone,
I have a problem about focusing. For instance, i have a toolbar at the bottom of
page with buttons in it, one of buttons causes the creation of a new popup
window via pgNewPopupAt function. After this point, i had no longer access to
the buttons in the toolbar, as long as the popup
Hi everyone,
I have a problem about focusing. For instance, i have a toolbar at the bottom of
page with buttons in it, one of buttons causes the creation of a new popup
window via pgNewPopupAt function. After this point, i had no longer access to
the buttons in the toolbar, as long as the popup e
