Skip to main content

New Edit Property/Method Dialog Replacement Available

Doug noted it here and if you haven't used it yet, it's definitely worth the download for Visual FoxPro.

I've been using this tool for creating properties so often now that I've forgotten what the original one looks like. Now, they've taken it one step further with the addition of Marcia's Edit Property/Method dialog. Doug's post has a rundown on more of the new features but this new piece totally rocks, making both dialogs dockable and non-modal.

How does that help developers?

You write code and decide that you want to need a new property or method. Habit kicks in and you close your code dialog and click New Property. Now you can't remember the exact name of the property. No problem - open up the code window (while the New Property dialog is still visible) to create it. A lot less trouble closing and opening windows.

Having the Edit dialog being non-modal makes it also really easy to document properties and methods (if you don't fill in the description, you're just making your code harder to maintain).

And I love the ability to switch between Property and Method on the fly in the New dialog - boy, I've made that mistake so many times.

I do have some gripes/wishes but that's WHAT the VFPX project is all about - you want to make changes? Go for it. Either submit them in as wish lists or join into the project and make the changes yourself.

Here's mine - so now I just have to make the changes on my side, test them out and then see about getting them into the full code base:

1. In the Edit dialog, why not have an option to hide the standard PEMs so you're only looking at custom ones? (for that matter, if you're going to show them, why not let us Edit them - this could almost act as a replacement Property window to some extent - and yes I KNOW that's not its scope)
2. In the New Method dialog, we need an option to immediately Add and Edit (as well as add and close).
3. Font options - this is always a tough one - some people like their custom apps (or non-built in tools) to look different - I'm not sold on it - so I would love an option to make the entire UI standard with regards to Font size.

One of the great things about this tool is that it highlights a feature in VFP that very few take advantage of (It seems like Doug has been promoting it for years now) - the ability to completely change what various built-in menu options do. The Help file goes into full details of how it works.

Comments

Doug Hennig said…
#1 is a very common ER, so count on it being done. #2 is an interesting idea; I'll add it to the ER list. #3 is also a great idea; I definitely want a larger font myself (MS made me use Tahoma 8).

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...