almost stable release: release candidate!

[SwordPlay]

I really like the new improvements, especially mouse control..
My CUSTOM crashes when I try to switch the gfx back end.

edit: rather, the program hangs/freezes. I tried switching the back end with Ctrl-F8 again but nothing happens, and the window can be resized but the contents are not updated

EDIT: using Ubuntu

[TMC]

Hmm, OK, I guess I'll just hide that option until/if it can be sorted out. What OS are you using?

I made menu items not highlight when the mouse is off the window.

[Bob the Hamster]

Is there anybody out there who hasn't tested a current nightly wip build? I am getting eager to call it a Release Candidate.

[TMC]

(I could just leave in the option to switch backend, with a big warning that it may crash)

[Bob the Hamster]

(I could just leave in the option to switch backend, with a big warning that it may crash)

That sounds fine. Should get us plenty of testing feedback, while adjusting expectations that it isn't always going to work :)

[Bob the Hamster]

Okay, I am now declaring the current nightly builds to be "release candidates"

That means that they are more or less the same as what will become the dwimmercrafty stable release, possibly as soon as next thursday!

Also, tmc, I know you are still busy-- is there anything special related to the git-svn bridge that I need to do when I branch /rel/dwimmercrafty ? Is it automatically going to add that subversion branch as a git branch? Or do I need to wait for you to manually add that branch to git?

[TMC]

I got back from Australia two days ago. So less busy, but still pretty busy for a few more days. I'll finish off a few more bugfixes.

Any new svn rel/* branches should be automatically added as new git branches by git-svn.

This thread hasn't seen much activity, but behind the scenes some other bugs were reported, and fixed by James.

[TheLordThyGod]

I'm using a relatively recent nightly, but not the most recent. I'm also still using the software at a pretty superficial level (there are features I'm not using), but so far it's been working fine as far as I can tell.

[Foxley]

The white border thing is still occurring, under these conditions:

A Windows Aero theme is enabled in Windows 7
Border Padding setting in Personalize is more than 0 (it's 4 by default)
sdl graphics backend is used (doesn't occur with directx or fb)

This is Custom with directx:


And Custom with sdl:

[TMC]

What happens when you resize the window? Or switch to fullscreen and then back to windowed? Does the border disappear? If you make the window slightly larger and then return to the original size, is the window size reported as 320x200, or something else? That looks like 324x204.

[Foxley]

If the window is moved, resized, put into fullscreen or pretty much anything, the line border goes away.

Is there a hotkey that shows the screen resolution? Or does it show up in a debug log?

EDIT: cdebug.txt says the screen resolution is 640x400.
https://www.dropbox.com/s/26uncme567sp7 ... g.txt?dl=0

[TMC]

Thanks. There's no such hotkey.

Is anyone else using Windows Vista+ (especially with the Aero glass window borders)? Does this occur for you or doesn't it?

I looked at the SDL changelog for fixes, and I doubt there. Maybe setting the window size to 320x200 another time would fix it (although it's already done 3 times!), but that could cause other glitches. So I'm inclined to leave it as it is for now, but switch back to gfx_directx at the next release.

[Bob the Hamster]

I'm thinking this thursday for the stable release

The only thing on my list of must-get-done before then is to clean up the distrib scripts to make sure I am properly building and uploading both the linux 32bit and 64bit versions of the stable release.

Yesterday I snuck in a small visual improvement to all bitset editors:



That should hopefully eliminate any confusion about which bits are on/off when using the mouse.

Mouse support is still quote incomplete and experimental, but I am happy we have made progress on it.

The other day I was testing changing integer values with right-click + mousewheel. I was skeptical when I read that one in the changelog, but it actually feels pretty natural.

[kylekrack]

That should hopefully eliminate any confusion about which bits are on/off when using the mouse.

fanTASTic. That looks so much better. One of my complaints about the mouse functionality was that when you were using the keyboard, the mouse highlighting just gets in the way, even if you move it off the window.

[Bob the Hamster]

.... the mouse highlighting just gets in the way, even if you move it off the window.

TMC fixed that already, when the mouse is off the window, there should not be any mouse highlight anymore