Once an mdi child is maximized, all mdi children are maximized. This is not always desirable, and the solution is to "fake" maximize the MDI child windows. Today we'll begin to template that, plus add a feature where the caption is removed so the fake maximized window can't be moved (and will appear "docked"). Also, as a bonus, we want to add tabs to the top for switching between fake maximized mdi child windows! And we're winging the whole thing!
This week, we've assembled a panel including Bruce Johnson, Andy Wilton, and Mike Hanson to answer your Clarion-related questions!
For example: Applications are changing, and how people interact with applications is changing. What worked well yesterday, doesn't work so well today. What changes in your existing app's design should you be making to meet your user's needs? Should you be considering mobile? Should you be writing your own accounting routines or hooking in to existing service via API calls? Or is everything fine just the way it is?
Our POS program has had a Touch Screen designer for over 20 years. Written using Clarion controls, it works well. But the button drawing can be a bit slow, and the designer looks "old". Today I'll be showing how I've used the Flowgraph wrapper from noyantis, along with the Property Grid and Report Control to update our Touch interface.