[Coco] Full GUI DriveWire 4 beta

Aaron Wolfe aawolfe at gmail.com
Wed Dec 29 18:55:20 EST 2010


On Wed, Dec 29, 2010 at 6:32 PM, Steven Hirsch <snhirsch at gmail.com> wrote:

> 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?


I could, but a user on the CoCo or another client could still enable
or disable it after I draw the menu but before you click on an item.
Changing how a menu is displayed on the screen for several moments due
to the setting at one moment is still letting the client maintain
server state, and I dont want do that.

I'll just make the commands fail in a normal way, essentially the same
thing that happens if you try to do other things that don't work. I
don't see people turning MIDI on and off very often, and I think its
even less likely that someone who has turned it off will spend much
time trying to use it.


>

>

> --

>

> --

> Coco mailing list

> Coco at maltedmedia.com

> http://five.pairlist.net/mailman/listinfo/coco

>

>




More information about the Coco mailing list