Re: [Blockbuster-devel] What's left?

[Robert E. <pa...@tu...>]

>> 1. I think we're supposed to display the current movie size (width x 
>> height) somewhere.

A fifth status line?  (Which size - original size?  Region of interest in 
pixels?  Region of interest in zoomed pixels?)

>> 2. The level of detail control in the GUI doesn't work properly.  It 
>> seems to fight going to level 0 when using the 4kx4k test file.

?

I'm not sure I'm seeing this (well, since I'm using the same file, I must be 
seeing it, but may be interpreting it incorrectly).

If the GUI sends back a level of detail that the application refuses to 
acknowledge (likely if the level gets clamped), the application will tell the 
GUI to update its level of detail value to the value being used.

Depending on the situation, this could appear to be a "fight".

The correct answer is to dynamically update the range of the LOD slider based on 
the current zoom and the available levels. (Brian, I'll try to figure out the 
math after handling a few other things; if you get to it before I do, the UI 
call is ReportRateRangeChange(), which must be checked to be non-NULL before 
executing.)

>> 3. The original spec calls for a slider to control zoom.

Is such still wanted?  We're at the point where the toolbox is becoming bigger, 
and I'm not sure the extra tool is useful (given that mouse button 2 performs 
the same function).

I know it's in the spec; we're just far enough out of spec already (supporting 
multiple renderers & user interfaces, for example, when only one was desired) 
and close enough to final release that I'd like to be sure it's still wanted.

But hey, it's easy enough to remove the tool if you don't want it, I suppose.

> 5. The frame rate slider should go to 100 at least, or have an infinity 
> option.  Perhaps a spinbox would be better.  Another problem with the 
> slider is that it's hard to make 1 fps increments/decrements since it's 
> so short.

Spin box is fine with me.  Maybe I'll put it in the same box with the detail 
spinbox (saving real estate).

> 6. We should compute do a zoom-to-fit upon first loading a movie.

When loading a new movie, yes?  In most cases, a startup movie creates a canvas 
of the appropriate size, and doesn't need a zoom... or would you rather have 
consistent behavior any time a movie is opened?  Hmmm, maybe I would too.

> 7. Do we want to have the LOD automatically reduced when we can't meet 
> the desired frame rate?  That could be a bit tricky.

Oh, yeah - and we're supposed to drop (temporarily) to LOD 0 when we pause the 
movie, too!

papillo the awake