[Coco] Full GUI DriveWire 4 beta

[Steven Hirsch]

On Wed, 29 Dec 2010, Aaron Wolfe wrote:

>>> Thinking about the midi stuff.. there is no "initial config read", the
>>> items are read from the server every time you open the configuration
>>> dialog.  this is because they can be changed at any time from the coco
>>> at the os9 prompt, or even from another client.  I gave up trying to
>>> maintain any sort of consistent state and just read everything as
>>> needed, every time, everywhere.  There is no persistent connection
>>> between client and server either, each action you do that needs to
>>> know something about or tell something to the server is a new session.
>>> This makes a couple things odd, but overall I think it's the best I
>>> can do.  So... my point is that the client doesn't know if MIDI is on
>>> when you pull down that menu, and it won't know if you've turned it
>>> off since the last time you pulled down the menu.  I'll have to just
>>> make it fail as politely as possible I guess.
>>
>> No problem.  When the server reports back that midi is suppressed, maybe you
>> can gray out anything underneath the pulldown?  Then, if it appears again,
>> you just cause the pulldown to fill in.
>
> The problem would be that unless you try to do something with MIDI,
> the client would never know whether it was turned on or off.  The
> client does not maintain any information about the state of the
> server.

Understood.  But can't you capture the event when the user pulls down the 
MIDI menu and poll to see if MIDI is disabled?


--