How about Application Display Programming (SC41-5715), Chapter 6? I'm not online right now, but I'm thinking there may also be examples in one of the files in QUSRTOOL.
Dale, if you're not online, how did you post the reply?
Just an FYI, some of these DDS keywords don't play nice with some 5250 emulation packages or thin clients. We made an attempt to use mousebutton selection, but the user base either couldn't access the functionality (thin client displays) or complained greatly that they lost the ability to draw squares for copy&paste, the mousebutton started to return function to the program (like the enter key does), and some windows usage of mouse selection didn't work when the emulator was running in full screen mode or the mouse cursor was within the confines of the 5250 emulator window.
The result was we pulled all the mouse code from the programs, so I don't have any samples anymore.
Online to an IBM i on POWER
Graphical keywords work fine on PC5250. Plain TN5250 tends to give a non-graphical appearance. Radio buttons become numbered lists, check boxes give you 1-char selection fields for each list item, and so on. Menus work. Though I never did try mouse operations.
But, Neil, I feel your pain. We had a package that used JWalk. Licenses came from the package vendor, so we did not have an in-house copy of the Designer tools. Home grown displays were under dynamic transformation. It doesn't even do as nice a job as plain TN5250. For the most part, I had to avoid the GUI keywords.