[futurebasic] Re: [FB] Three Questions QT/runtime speed/menu graphics

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

From: PRITCHA@...
Date: Thu, 21 Oct 1999 11:16:13 +0100

Orig Post:
>> Hi Guys,
>>
>> Three Questions:
>>
>> 1) Still haven't been able to get PICTs into Quicktime.
>> I suspect it should be easier with FB^3...
>> There's example C code to do this but I couldn't get it to work with FBII
>> despite creating the ToolBox glue code.
>>
>> 2) Having just reviewed some software for my kids - it ran way too fast on my
G3
>> -
>> how would you go about designing s/w that ran acceptably on any machine
>> speed? Presumeably do all updates on a click tick?
>>
>> x=x+speedx*timeframe
>> y=y+speedy*timeframe
>>
>> Anyone got any example code?
>> (I guess someone's going to say FJIII... I should look before I ask -
>> apologises in advance)
>>
>> 3) How do you put graphics into Menus?

Chris Wyatt wrote>

>Try Menu Mill on the FB^3 CD for putting graphics in menus.

G'day Chris,

I've seen Menu Mill - as an example App. I didn't see any
description of how to put the graphics in the menu.
Hey, I didn't see any description at all!!! :-)

Paul Bruneau wrote>

>Hmm, how would you compute timeframe?

I was thinking about...

timeframe = Tick Count (now) - Last Tick Count


>I would suggest a "turns based" kind of deal, where each "turn" was
>allowed to occur after a certain length of TIME (time is in all caps to
>differentiate it from any other measurement you might take from a
>computer like loop counts, etc, which would be dependent upon machine
>speed.) Time is never dependent on machine speed. It keeps marching.
>So instead of x=x+speedx*timeframe, I would use x=x+speedx but only call
>it after enough time has passed since the last call.
>I hope I was clear. I'm often not :)

Yes, but wouldn't that might produce "chunky" animation steps?
I was hoping to improve the quality of the animation if there was
enough processing power to do so, without removing responsiveness to
controls.
(In Quake for example, the "frame rate" varies with processing power
and level of on-screen detail).


Derek,
You seem to be the resident FB, C and Quicktime guru.
Is there anyway I can bribe you to developing a PICT to QT
routine? :-)

Andy