On Feb 27, 2008, at 9:45 AM, Paul McNett wrote:
>> The issue, though, is that this would force people to enclose every
>> single string (which will be the majority of entries, at least in my
>> experience, in quotes. IMO, it is exceedingly poor design to require
>> extra stuff for the default case.
>
> OTOH, a simple solution that provides for all cases can be a good
> starting point.
Simple for programmer != simple for user.
It might be simple to implement, but requires more work from anyone
using the tool.
>> This may be a specific solution for the Class Designer use cases,
>> but
>> in every situation I can think of, the options entered in the dialog
>> will all be the same type. Adding a selector to specify the type that
>> the entries should be might be a workable solution.
>
> You'd have to allow None in all cases. Anyway, I think saving the
> strings to be eval'd in the XML should be considered, even if you
> aren't
> showing the extra quotes in the designer.
I've already done the XML stuff; if you edit the values in the cdxml
file, they work just fine in the Class Designer and runtime
instances. The only thing that breaks is the dEditableList control.
That's the limiting factor that's causing the problem.
-- Ed Leafe
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
Searchable Archives: http://leafe.com/archives/search/dabo-users
This message: http://leafe.com/archives/byMID/dabo-users/[EMAIL PROTECTED]
