[futurebasic] RE: RE: [FB] Platinum look

Message: < previous - next > : Reply : Subscribe : Cleanse
Home   : September 1999 : Group Archive : Group : All Groups

From: Ken Shmidheiser <kshmidheiser@...>
Date: Mon, 13 Sep 1999 10:00:54 -0400
Concerning FB^3's compliance with Appearance Manager Bill Michael responded,

> >In my initial post, I asked if FB^3 is Appearance Manager compliant,
> >but my question remains unanswered.
>Sorry - the answer is rather unclear to me... but I'm 90% sure it's
>"yes". Not having worked with AM myself in FB^3, I'm relying on my
>(notoriously bad) memory of discussions on the beta list. That _may_ be
>one of the two or three things on the "wish list" that didn't make the
>cut for Release 0, having to wait for Release 1; but I _think_ it's all
>been done. Anybody else have a more definite answer?


I probably should have better clarified my definition of "compliant."

As noted in the earlier posts, FBII's BUTTON statement falls short of 
directly handling many of the new controls. What I am hoping to see 
is some kind of extended BUTTON statement that will allow setting of 
the additional parameters. Better yet would be a new CONTROL 
statement that specifically addresses advanced control settings, 
i.e., isVisible%, currValue%, cMinValue%, cMaxValue%, CDEFid%, etc.

In the past, handling controls has been a "roll your own" experience. 
There's nothing wrong with that, but it took a lot of time, trial and 
error to create your own icons, code the CDEF and CNTLs in ResEdit, 
and get it working. Then you   still had the concern of it breaking 
in a future system release.

With all the new and attractive controls already built into the 
MacOS, it would be nice to easily call them directly from FB^3. Why 
reinvent the wheel?

Thanks again for all your hard work on the list.