PEM Editor Version 6.10 Beta

(Released 2010-10-10)

Project Manager Jim Nelson

Click here to download

Enhancements in this release

This release has enhancements dealing with multiple objects: a new form for editing properties when multiple objects are selected, and a new search tool for selecting objects.

Editing a property for multiple objects

When you have selected multiple objects with your mouse, there is a new form for editing the properties for the selected objects. Ctrl+Click on a row in the PEM Editor's grid to bring up the Results Form:


You can double click on the value of a property to edit that property, or double-click on the name of the object in the first column to navigate to that object.

You can also add, remove, resize, and re-order the columns.

Searching for objects

There is a new search tool for finding objects in your form/class that meet criteria that you specify. This allows you to specify (find) objects and then modify their properties, using the new form displayed above, and also to navigate between the objects.

Searching is initiated by using the new Binoculars Icon at the top of the PEM Editor form:


This brings up the new 'Find Object(s)' form, which allows you to enter your own search expression to find objects in your form or class. The result of your search is displayed in the new form (above) for editing properties for multiple objects.


Objects which match the search criteria are displayed in the Results form (shown at the top of this release page).

Last edited Oct 11, 2010 at 1:29 AM by JimRNelson, version 28


eselje Sep 1, 2010 at 10:54 PM 
Oooh, that'd be good too. But setting a ControlSource is beyond the scope of this app, no? Unless you could do it with one of those new IDE Tools like your "beautify".

JimRNelson May 19, 2010 at 5:07 PM 
eselje --
When you add a new property, you want to prompt for what control to bind it to?
Off hand, I think I would like it another way ... I think that when I set the controlsource to Thisform.something, that it creates Thisform.something for me.

JimRNelson May 19, 2010 at 5:05 PM 
Mike -- re problems with Preferences colors -- try this link, to the latest version ---

Note the the Preferences form has been extended, and there are new tabs for Beautify and simplifications for resizing/anchoring. But remember that, this is hot off the press and Beta ....

eselje May 18, 2010 at 5:47 PM 
This is awesome. Feature request: When I add a new property, allow me to select which control on the form I'd like to set the controlsource of that property to. Since it's really smart, it could even deduce that if the property begins with 'l' it's going to be a checkbox, etc. Thanks!

MikePotjer May 17, 2010 at 6:13 PM 
It doesn't matter if I select 'ForeColor', 'BackColor', or anything else. They simply are not doing anything. And as you noticed, the color buttons are always visible now.

JimRNelson May 12, 2010 at 9:48 PM 
What have you selected for the comboboxes to the left of the color buttons? The color buttons only apply if you have chosen ''BackColor' or 'ForeColor'.

(Actually, they should only appear in that case -- that is something for me to fix)

MikePotjer May 12, 2010 at 1:36 PM 
In PEMEditor 6, in the Preferences, under Grid Highlighting, none of the color buttons do anything, so I can't set any custom colors.

JimRNelson May 6, 2010 at 11:38 PM 
Eddie --
Sorry about these problems -- I know better than using ICASE!! ... and I will also correct the reference to dockposition. I hope to have resolution for both of these issues, as well as the Buffer Overrun, soon.

EddieC May 6, 2010 at 2:49 PM 
In vfp8, i get the error "Property dockposition not found" in pemeditor::setcurrentselectedobject when i click on the 'parent' button next to the dropdown list of controls. Seem to also get the same error if I choose an Object from the drop down list, but not if I choose a method from that list.

EddieC May 6, 2010 at 2:28 PM 
In vfp8 cannout compile because ICASE function is used in editproperty.vcx
In vfp8, when i try to use the Open Button (open form, open class, etc) it says ANCHOR is not defined.
Thanks for the great work !

ljr1981 May 6, 2010 at 2:05 PM 
Causes Buffer Overrun errors that wipes out VFP 9 SP1 for me whenever I open a form (VCX or SCX based). Classes are OK and do not break, but forms do.