Hi!

I catch self quite often that it would be good to preserve MixedCase property names. Preoprties editor sorts uppercase PEMS first, then lowercase. When you have long property name, it is hard to find it without accurate examining of the most of the list of properties. MixedCase approach is used in naming cnventions for a quite long time, but we still do not have it used for the VFP properties. Specially it is useful when creating your own classes for framework. It would be good also to define your own controls for editing property value in the properties list, like a color picker, combobox with choises, file selection etc. Finally, very bad thing that we cannot put value into property longer than 255 characters. VFP memo field (where properties stored) allows any data with any length, why such limitation? I still require to write long SQL SELECT statement into property in the INIT of the control. With grids it works bad, because assignment of SELECT statement in the INIT cause re-binding of the control sources for each column. Long lable caption and ToolTipText for control also require to be assigned in run-time. Custom properties often get long values too...

There are many little things that together make property editor not comfortable when creating classes and working with properties.

It would be good also to have custom groups like in the VB.


>>I would like to use mixed case method and property names. Why does VFP insist making them lower case? Is there some innane reason?
>
>Based on what I see in the VFP source code, it has a lot to do with VFP's general case-insensitive nature. In C++, you can have a function called MyFunction, and have another called MYFUNCTION, and they're both distinct functions. VFP makes no such distinction.
>
>VFP7 does allow for case distinction in the COM server typelibs, however.