[Ohrrpgce] [Bug 683] RELEASE: Ypsiliform

[bugzilla-daemon at karnov.dreamhost.com]

http://rpg.hamsterrepublic.com/bugzilla/show_bug.cgi?id=683

--- Comment #20 from Ralph Versteegen <teeemcee at gmail.com> 2009-12-11 11:22:01 PST ---
(In reply to comment #19)
> (In reply to comment #18)
> > (In reply to comment #17)
> > > Any objections to a Friday release?
> > 
> > Excuuuse me, I think you mean "Any objections to a Friday release candidate?"
> 
> Sure, *cough* that's what I meant ;)
> 
> Actually, I literally meant a release. I feel that the wip has been MORE than
> stable enough to be a release for more than a month, and right now I feel like
> we are in danger of moving away from stability rather than towards it. (I
> understand that might be an irrational fear)

Well alright, however if we do switch to gfx_sdl, then we definitely need a
release candidate. Actually it's more like the other way around: a gfx_sdl
release candidate would tell us whether to change the backend.

> > Anyway, yes I do; I've been meaning to post the following, Things To Be Done
> > Before Release:
> > 
> > -change resetgame
> > -change get/setboxborder
> >  (since these are breaking changes, they really should be done before the next
> > stable release)
> 
> Change resetgame how?

As promised to resolve bug 777 (rather, feature request).

> Also, if they are breaking changes how are we going to do them in a way that
> doesn't break anything?

By keeping the existing command ids and mapping the command names to new
commands in plotscr.hsd.

Well, for get/setrectborder anyway. I'm pretty sure we can get away with
changing the way resetgame works, since there's currently no point using it
instead of gameover in the cases for which I want to change its behaviour.

> > -determine whether the default graphics backend should be changed to gfx_sdl.
> 
> Hmmm... probably.
> I feel pretty good about the gfx_sdl backend right now.
> In fact, I am going to make it the default for Linux right now. I am agreeable
> to make it the default on Windows too (depending on the gfx_directx descision)
>
> > (bug 766, bug Complaints of phantom keypresses when using gfx_fb are coming in
> > thick, and faster all the time;
> 
> Really? I hadn't heard any. Phantom keypresses? Like randomly?

bug 785, bug 753,
bug 334, a more severe version of which was reported here:
http://www.castleparadox.com/ohr/viewtopic.php?t=6450
http://rmsephy.livejournal.com/231215.html

In addition, switching backends gets around bug 185, which is very annoying,
experienced by many people, and happens 100% of the time for me on both my
computers (but with different symptoms); plus bug 766, and I thought there was
another...

However, I need to get around to that testing on bug 796, plus I've just
experienced a serious bug with the pause key in gfx_sdl, which I can fix.

> That sounds cool... but doesn't that mean linking in two separate backends?
> Wouldn't that be a major architectural change? But you know the backends better
> than I do, if you think it is reasonable, I am game.

Would require a set of function pointers and a very small wrapper to
dynamically load gfx_directx.dll.

-- 
Configure bugmail: http://rpg.hamsterrepublic.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.