[Ohrrpgce] [Bug 683] RELEASE: Ypsiliform

[bugzilla-daemon at karnov.dreamhost.com]

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

--- Comment #19 from Bob the Hamster <Bob at HamsterRepublic.com> 2009-12-10 09:28:45 PST ---
(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)

> 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?

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

> -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?

> so far I only know of one person who actually
> tried an alternative backend (and said that fixed the problem).
> In addition since gfx_directx is done, and is far superior to all other
> backends, it would be great to see whether we can use it by default, and fall
> back to something else if the user doesn't have DirectX 9 support. This is
> definitely worth delaying release for a couple days for.

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.

> -I have not filed it on bugzilla, but NP and I ran into what appears to be
> another slice tree memory corruption bug while testing the A* pathfinding
> scripts for his game. I just keep getting distracted.

If you file it with the test case, I'll gladly help you track it down.

> -Add an error reporting level selection in Custom. I'm actually very pleased
> with how much easier it's become to debug scripts - as long as you use the
> -errlvl commandline option.

Yes, the new script debugging tool is frikkin' fantastic. I love it.

> -I was going to add "Fix the current directory problem properly", although it's
> not very important. The problem was that the current directory is used for many
> different things: placing the log files, the default import directory when
> browsing, the export directory for screenshots, tilesets, textboxes, etc, and
> who knows what else. Changing the current directory was the wrong solution,
> instead the current directory shouldn't be used.

I think I have fixed the worst of the side effects of changing the current
directory, but not changing it would be nice too. Not a big deal releasewise
for me.

> I've got several large things in progress in my working copy, but which I can
> finish up quickly.

Okay. I'll wait.

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