[Coco] Full GUI DriveWire 4 beta

[Aaron Wolfe]

On Wed, Dec 29, 2010 at 6:18 PM, Steven Hirsch <snhirsch at gmail.com> wrote:
> On Wed, 29 Dec 2010, Aaron Wolfe wrote:
>
>> On Wed, Dec 29, 2010 at 5:46 PM, Steven Hirsch <snhirsch at gmail.com> wrote:
>>>
>>> On Wed, 29 Dec 2010, Aaron Wolfe wrote:
>>>
>>>> Ok.. well I can't explain or reproduce this behavior.  It's working
>>>> fine here on linux 64, so I think it will be best to just wait for me
>>>> to make a package and we'll see if the one I build works any better
>>>> for you.  I want to sort of the display issue, the fonts are too big,
>>>> but once that is done I'll make packages for all the platforms.
>>>
>>> And, naturally, after I cleaned up and rebuilt both server and UI from
>>> scratch (for about the fourth time), things started working.  It
>>> "remembers"
>>> all parameters now.
>>>
>>> Spotted a bug, I think:  I have MIDI disabled per your suggestion, but
>>> the
>>> UI really has problems when you use the MIDI pulldown under that
>>> circumstance.  Probably should be picked up on the initial configuration
>>> read and be grayed out on the UI?
>>>
>>
>> BTW if you have time, can you grab the latest UI and see if the fonts
>> either 1: look ok and fit properly, or 2: can be fixed by adjusting
>> the new "Dialog Font" parameter in the UI settings?  It seems there
>> are very few fonts that exist on a stock windows, stock mac, and stock
>> linux system that don't look awful.
>
> Unless I make the dialog font too small to read comfortably, labels are
> getting truncated.
>
>> 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.

>
> --
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>
>