From: John Adcock <John@ad...> - 2007-03-04 15:16:48
What is the current status of all the recent changes and who is doing
I'm happy to pick up some slack next week but I don't want to pick up
anything that other people are looking at.
Here's what I think is going on.
Schedule changes don't compile on VS6, needs to be fixed before next
Torsten hasn't got combo boxes, needs to be replicated
The DX9 display code is alpha and we shouldn't wait for that to be fixed
beyond any crashing.
What have I missed?
> Schedule changes don't compile on VS6, needs to be fixed before next
Same problem with Express and SDK plus DDK.
> Torsten hasn't got combo boxes, needs to be replicated
> The DX9 display code is alpha and we shouldn't wait for that to be
> fixed beyond any crashing.
> What have I missed?
Because of the new DX9 support I think we break W95 machines again where we
last time worked on to get it back. I'm voting to make first an version with
the new driver but without DX9 flaged 'W95 last time supported'. CVS in the
middle last year is good point.
From: Rob Muller <rob.muller@gm...> - 2007-07-27 01:34:14
At 17:19 04-03-07, John Adcock wrote:
>What is the current status of all the recent changes and who is doing
Sorry about being so slow. I am ready for a new release.
Unfortunately I can't figure out the problem with the constant 25 or
17 dropped frames per second. For some reason the latest official
Dscaler release (the version I use daily) stopped showing the
problem. Unfortunately the latest development version still has the
problem (even with the same ini file).
Get latest updates about Open Source Projects, Conferences and News.