Skip to main content

VFP 9 Cool Feature: Dockable Windows

As shown in the image below, the new dockable windows feature in Visual FoxPro can be a lot of fun. Forms now have a Dockable Property with the following values:
 
0 - Docking not permitted
1 - Supports Docking and Is Dockable
2 - Supports Docking but is NOT dockable
 
Huh? What does value 2 mean? It means that while the form will look like a dockable window, it cannot be docked. Users can make it dockable by right-mouse clicking on the title bar and choosing Dockable. They can also do this by selecting Dockable from the Window menu.
 
What does a dockable window look like? Essentially, it uses the half-height title bar property in VFP.
 
Having a dockable window also means your resize event better be smart. When a form is docked with another form, the resize method for BOTH forms is called. As well, if you dock two dockable forms at the top of the screen, the form that contains both docked forms now becomes a tabbed dialog with the tabs at the BOTTOM of the screen (i'll post an image).
 
Note: Dockable forms only work for applications that use the Visual FoxPro desktop. So if you are using top-level forms in your applications, be advised that the Dockable property won't work.
 
How will applications use dockable forms? At first glance, it really appears to be a feature that will be used heavily by framework apps and other tools that integrate directly into the FoxPro development environment, but there are certainly some types of applications where they will be handy. For example, in a number of my applications, we put a "message" or "alert" bar into the toolbar. The problem with this is that if the message uses an edit box, it screws up the entire toolbar height and width. With a dockable window, the alert message can now attach itself on the main screen to which it applies.

Comments

Anonymous said…
I was really looking forward to dockable forms in VFP. I had tried to build this feature into my forms earlier, but gave up.

I am very dissapoined though that the dockable feature only works for forms within the Visual FoxPro desktop. I wanted this for top-level forms, which is where I think it would actually be usefull. As it is, I don't see that I will ever use this feature, as I only build applications that run via top-level forms.

Popular posts from this blog

Blogs and RSS come to Microsoft.com

MS has just introduced their portal and it's pretty comprehensive. Nothing quite like learning that some people use AIM instead of MSN messenger, or that there really may be a need for supporting 4 monitors ( Cyrus Complains ) However, it's really a great sign that MS is serious about supporting the blogging community which seems to have um, exploded in size in the past year. Blogs and RSS come to Microsoft.com

Elevating Project Specifications with Three Insightful ChatGPT Prompts

For developers and testers, ChatGPT, the freely accessible tool from OpenAI, is game-changing. If you want to learn a new programming language, ask for samples or have it convert your existing code. This can be done in Visual Studio Code (using GitHub CoPilot) or directly in the ChatGPT app or web site.  If you’re a tester, ChatGPT can write a test spec or actual test code (if you use Jest or Cypress) based on existing code, copied and pasted into the input area. But ChatGPT can be of huge value for analysts (whether system or business) who need to validate their needs. There’s often a disconnect between developers and analysts. Analysts complain that developers don’t build what they asked for or ask too many questions. Developers complain that analysts haven’t thought of obvious things. In these situations, ChatGPT can be a great intermediary. At its worst, it forces you to think about and then discount obvious issues. At best, it clarifies the needs into documented requirements. ...

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction...