setting pointer location

[David Vaughan]

On Sunday, Dec 29, 2002, at 11:08 Australia/Sydney, Alan Gayne wrote:

> Let me know how it works out.

I like it. The card has two groups (not in the Rev sense but logically 
connected) of fields plus sundry other data. I use two modeless dialogs 
to complete each the two field sets when needed. The user brings up the 
dialog by clicking in any of the relevant fields, and can save changes, 
leaving the dialog visible, do something else, or dismiss it without 
changes (buttons are Delete, Clear, Save and Close). If, having brought 
it up, they click a second time in the source fields then the new data 
simply replaces the old (removing unsaved changes) in the dialog and 
not affecting the source data previously selected. In normal use there 
is no significant difference between having it modal or modeless but 
the latter is a slight advantage to me where the user can pause to 
adjust something else, affecting a calculated field, before completing 
the dialog fields.

regards
David
>
> Alan
>
> On Saturday, December 28, 2002, at 04:53 PM, David Vaughan wrote:
>
>>
>> On Sunday, Dec 29, 2002, at 08:16 Australia/Sydney, Alan Gayne wrote:
>>
>>> Hi David,
>>>
>>> Why "modeless" instead of modal dialogs?
>>
>> Alan, because I imagined (I haven't written it yet) that the dialogs 
>> could float about, available, and used simply by bringing them to the 
>> front. The entry fields they are replacing are modelessly available 
>> after all. I will see what works.
>>
>> cheers
>> David