>>Hi folks,
>>
>>I've been working in a new class for creating charts, and had to add lots of custom properties to it.
>>
>>I've been using Doug Hennig's new property editor, in order to automatically generate the memberdata needed to keep the captions of the properties the way I kike them to look.
>>
>>But I've reached the 8K limit for a property.
>>
>>Is there a workaround for this ?
>>
>>Thanks in advance
>>
>Cesar:
>
>Just a couple of simple ideas:
>
>If you have properties with access and/or assign methods, go to Class - Memberdata Editor, and uncheck "Has MemberData" to all the access and assign methods.
>
>Do the same thing to all the "private" properties/methods that are only for use by the class internally.
>
>Add all the "public" properties/methods to Favorites, just so its easier to work with them.
>
>For new properties/methods with Access/Assign that you add with the new/edit property editor, never check the "Access Method" or "Assign Method" checkboxes, just add the property like for example:
>
>"MyCustomProperty"
>
>And then add the access and assign methods yourself, just like another method, but all lower case:
>
>"mycustomproperty_access"
>"mycustompreperty_assign"
>
>For "private" properties/methods, just add them all lower case.
>
>If you have lots of Assign/Access methods and lots of "private" properties/methods, this will shave off a lot from Memberdata.
>
>This could be a great feature to add to the new/edit property dialog, a "Add Assign and Access Methods in lower case" option.
>
>Hope this helps.
>
>The real problem is all this memberdata thing, isn't it? I wonder who was the genius that came up with this one, instead of doing things right.
>
>Carlos


Hi Carlos,

That's exactly what I decided to do in this forst moment.
Further, I hope to floow Bo's suggestion, separating the main parts of the charts as objects, in order to make it more clear for users to work with.

You are correct, in fact I have many methods and properties that used only internally, I'll have to remove theis memberdata.

That's really bad...

I was hoping to add some custom memberdata scripts to ease users access to some properties. Even putting the relevant functions in a separate prg, these scripts would need to consume some space from memberdata...

It's a pity they didn't prepare this from the beginning...
The vcx table has lots of free space, where most information could have been stored very easilly.

Unless Doug Hennig takes the courage, and starts recreating the Properties window as well...

Thanks !

Regards

Cesar