|
From: Damon C. <dam...@tc...> - 2005-07-27 16:27:19
|
> Damon Courtney wrote:
>> Actually, I'm adding this type of feature to the BWidget
>> Dialogs (and the new ChooseDirectory widget). I just added a
>> -name option to the dialogs that would provide a name for the
>> dialog, and they remember state from the last instance. Example:
>>
>> ChooseDirectory .d -name OpenImage
>>
>> That way, even though choosing a directory can be done in
>> many different places throughout an application, each one
>> remembers its state. I like this better than a global state
>> because I like to remember where the user was last when the
>> clicked this particular dialog.
>
> Isn't this redundant to the '.d' name already? If they reuse
> .d without destroying it, it should keep the info, otherwise
> they would have another named CD dialog, no?
Actually, the real purpose of the -name attribute is to make it easier
to create dialogs with a user state. IE:
Yes, No, No to All, Yes to All, Cancel
The user clicks "No to All," and the dialog remembers that based on
the name of the dialog. Then, any subsequent calls to create a dialog
with that name just immediately return a No. Of course, I'm not
exactly sure how to name that dialog.
MessageDlg .m -type yesnonotallyestoallcancel
Just doesn't seem like the right thing to do. 0-]
D
|