Pwnboxer is updated! 01/17/10 Update!

[Tim]

Pwnboxer is updated! 01/17/10 Update!

This update fixes 2 main things:

#1 - Major rewrite to the Pwnboxer Dockable Clickmapping. This was completely re-built to allow for an infinite number of Dockable Clickmapping buttons. You can also "lock" a set of buttons in place anywhere on the screen so you don't accidently move it.

#2 - Few misc. bugs were fixed that would cause the in-game Pwnboxer windows to hide themselves when you alt+tab'd through windows.

Grab the new Pwnboxer.com here: http://pwnboxer.com/download/

[Iru]

Bug report:

Just updated to the latest pwnboxer and it no longer displays any of my key mapping configuration. Worse still, having just checked, it has actively deleted them all.

Fortunately I copied my .pbcfg file so I can recover but this is not good.

EDIT: Well, I know why this happened - kind of. The format of the "Key Remapping" section of the .pbcfg file has changed. Consider this me reminding you about backward compatibility & release notes then

[Iru]

2nd bug report:

The auto focus on mouseover function appears to be having issues in this release. Previously application focus was instantaneous; mouse over the game 2-5 and the toon immediately responded to movement etc. Now there is a noticeable lag and occasionally I have to click in the window to get keystrokes to be recognized. Could thins be a weird interaction with the dockable clicking changes?

[Tim]

Iru,

Could you try rebooting and see if it still happens (the mouse focus). The rebooting is just to make sure Pwnboxer doesn't still have the old DLL loaded from the prior version.

As far as the key remapping, it shouldn't have any issues that I can think of. I don't recall changing anything there in quite a few versions. Any shot you can open up your .pbcfg from before and after and see if you notice what is different? I myself don't use the key remapping so I could have missed something

[Iru]

EDIT: I changed the zip file to have both the previous and the now working new file. Check the "Key Remapping" section to see the differences

Attached is the pwnboxer.pbcfg that was working prior to the latest update. Sorry about it being in a zip file; it's your forum software's fault. It wouldn't let me upload a 42k text file.

Try loading the configuration and you'll see what happens. I tested reloading that file after rebooting - in case there was a DLL issue - and it still fails the same way.

That same file may help with testing th the autofocus on mouse over issue. Rebooting did not fix the mouseover autofocus issue but I can offer some additional insight.
1) I play with a dual monitor configuration, as the pbcfg file shows, so this maybe something you're not usually testing.
2) The issue appears to be with correctly selecting window to focus on when the mouse is in monitor #2. Regardless of where I position the mouse on monitor #2, keyboard focus ALWAYS goes to the game in the top left corner UNTIL I explicitly click on one of the other games. If I click on games #3-#5, autofocus on mosueover works correctly UNTIL I return to monitor #1, where it fails again until I explicitly click

[TheMuffinMan]

Originally Posted by Iru

2nd bug report:

The auto focus on mouseover function appears to be having issues in this release. Previously application focus was instantaneous; mouse over the game 2-5 and the toon immediately responded to movement etc. Now there is a noticeable lag and occasionally I have to click in the window to get keystrokes to be recognized. Could thins be a weird interaction with the dockable clicking changes?

This is working without issue as it always has for me in the new version.

EDIT:
and I play on a triple monitor setup

[Iru]

Weird. The mouseover autofocus now appears to be working. Not sure what changed.

[Iru]

FYI: the game #2 grabbing the mouse when I mouseover into the second screen "feature" is back for me. If I can figure out what I'm running/doing that triggers it I'll let you know.

[PDXMike]

Tim--
Two things. 1st - MOTD that pops up when pnwboxer loads is NOT showing the update. 2nd - file naming is a bit confusing, ie I just went from version v02.01.1213.05 to the (newer??) v02.01.0113.01. I do see your logic in using release date as your version number, but without a YEAR it's not very helpful...