Quote from: PyroMan on July 11, 2013, 08:44 PM
I think we need a fix the way how Ctrl+Home works.

dont describe it. it was discussed a million times before and after 3.7.0.0. Deadcode just forgot to implement a fix. don't worry because I'll make sure he doesn't forget it this time

Quote from: j0e on July 04, 2013, 05:31 PMAnd I assumed the stretched mouse focus was impossible... just checking since you have made some breakthroughs recently with the frontend.

unfortunately those "breakthroughs" (there was only one recently btw which is right now) have nothing to do with that messy control window, on which every button, form, and graphics icons depend we have to thank Team17 for using MFC with such a poor implementation some decades ago. That's also the reason why current W:A maintainers don't change the way frontend works. One single change can break everything, and you may spend long hours or days trying to find and resolve the issues. We all hope for 4.0, but until then, this is the only real solution for now.
But still if you need to keep the big window running, just use Alt+Tab or something similar!

Quote from: j0e on July 04, 2013, 05:04 PM
Very awesome Steps.. I've been hoping for that 'Run frontend in background' feature... One step closer to perfect for multi-monitor users. The only thing that could improve it now is if the mouse didn't get trapped inside stretched/custom-sized frontend windows. So that it would work the same as the default (windowed) size where you can click into and out of the window easily. The way the default (windowed) size works is perfect now, but it's a bit hard to read with its small size.

Man, if it was possible, i'd do it the in the day this was released. But it is not. The current frontend is so buggy that all of its controls, as well as mouse listening is bound to top left angle. Moving that control window will also move any icons or menu elements out the window, leaving us with just sky and stars. There were many attempts at finding a solution to properly move the controls but that solution was never found. Kawoosh wanted to look deeper into it one day, but still didn't get to it.

QuoteThere's also a very small quirk with the Ctrl+G/Ctrl+H feature in-game.

When you do Ctrl+G/Ctrl+H the first time, the Ctrl+H has no effect. The Ctrl+G releases the mouse as intended, but as soon as you click outside the WA window, the window is no longer active. The Ctrl+H does not keep the WA window active in the background, and all animation stops.

When you restore focus to the WA window, Ctrl+G/Ctrl+H works as intended --- you can click outside of WA's focus and WA continues to animate in the background.

This doesn't happen for me. Can you show your settings file?

Edit: I understand what you mean there. You first press Ctrl+G and only then Ctrl+H. This will never work because you are not focused on the W:A window anymore (the keyboard keys only work when the game is on foreground). Do it in reverse. Or... you can just not press ctrl+g, because there's the new "AutoUnpin" feature. Btw, check out the "ActiveBackground" in ini file... It can be enabled permanently now.

A new update released, 0.5.5.0.

• Now got rid of the "2x size" maximum resolution limit! This means you can set any resolutions you like without any mouse issues, as long as your GPU supports it (maximum 2D texture size).
• Added the long-awaited Run frontend in background feature to prevent the frontend menus from self-minimizing when switching to another window. When it is enabled, the frontend will keep running in background. Now enabled by default, can be switched using the "RunInBackground" setting under [FrontendSettings].
• The built-in in-game mouse capture has now been improved to reflect the actual window's positions, just like done recently for ActiveBackground.
• The NoTopmost feature has been moved to the [Misc] section and now affects both frontend and in-game. Still can be switched with Ctrl+T, but this time in both places.

Quote from: Berria on July 03, 2013, 06:11 PM
ok i installed newest update,everythings was perfect, and after some days new problem just come alone:

when i wanna open worms i see this

well if you have a good memory, the solution to your problem was returning WormKitDS back (lol that post is still in this thread, man!_, but this problem still needs to be investigated. it is weird that while for everyone else it's fine, for you the game fails to load wkPackets using the built-in loader rather than WormKitDS

Quote from: JMK on June 30, 2013, 11:24 PMMy problem is minor so if there's no fix, no big deal.  I'm on windows 7 and have the taskbar at the top of the screen.  Both the menu and game screens appear at the very top of the window, under the taskbar.  For the menu, I don't care so much, and from what you mentioned earlier it isn't possible to move anyway.  What about the game window?  Would it be possible for me to move that down about 40 pixels?

when the match starts, the ingame window is centered automatically. as for the menu, a while ago I found a way to move it although this will require eating the mouse cursor and not letting it out. nevermind, it may not work properly with the latest fixes, anyway it isn't recommended...

A new update has been released.

• The ActiveBackground feature has been made available to be enabled permanently with a settings file. It is also finalized and now works in all cases. Window border in this mode is now possible, and the window is no longer stuck in top left corner.
• Users with Windows Classic/Simplified interface (no aero/DWM) are no more limited to top left corner, and they can now also use the border. ActiveBackground is always forced enabled for them, as before.
• Added TopLeftPosition feature for people who need the in-game window to be on top left. This can also be temporarily enabled with Ctrl+L.
• Added AutoUnpin feature which will automatically unpin mouse cursor when you switch to another window (alt-tab or any other ways). Enabled by default now.
• Mouse will now be pinned after clicking inside the WA's window if it was unpinned before. For stretched and expanded modes it will be re-pinned automatically when you get back to WA.

Quote from: j0hny on June 29, 2013, 03:20 PMsometimes end up spoiling colors

colors can not be spoiled on 3.7.x anymore, unless you purposefully enable 8-bit rendering, which you shouldn't do.
minimization is also smooth now (almost instant) on 3.7.2.1
your argument is invalid

Quote from: mbernal131 on June 29, 2013, 02:36 PMAs a side note, the weird thing about me enabling border before was that it actually helped me see the game. All previous wrapper settings failed, but as soon as I enabled border, I could at least see some of the screen. Weird huh?
 

yep that's weird.
glad to hear it's solved! I'll add this to the FAQ.

Quote from: j0hny on June 29, 2013, 09:18 AM
As to the second - the right key on the icon game, properties, compatibility, and select

rofl.
you don't need any of these options.

ah what a coincidence, I also use 150% dpi scaling but didn't meet these problems. Btw, WindowedFrontend and WindowedInGame are of course for two separate things: the first for the menus, the second for the actual gameplay (so it will change resolution there).
btw you should not enable Border, because it doesn't work as it should and breaks some things. if Border support was to be added, it would only work InGame due to the problems made in 2001 by Team17.
also in your case you should disable all of the WWPCompatibilitySettings; none of them applies to you.

now to DPI scaling. It probably scales some apps that it shouldn't, like WWP in this case.
Disclaimer: I don't know the English labels for the sections explained below, so you'll have to check it out.
So try either:
- go into WWP.exe properties, "Compatibility" tab, then check "Disable dpi scaling on high screen resolutions"
If it doesn't work, then:
- right click the desktop, "Screen resolution", then "Changing size of text and other elements". Choose "User-defined size parameters". Make sure that the "Use Windows XP scaling styles" is enabled. This option is there to prevent scaling some apps it shouldn't scale. In your case it's WWP; it scaled its entire interface thinking that it's merely a dialog window (in fact it is, but we have to blame Team17 for such a poor implementation). Which was a mistake.

Quote from: mbernal131 on June 27, 2013, 11:39 PM
Hello!!!

I'm hoping someone can help. I've downloaded the patch for Win7 and the game finally launches!!!

My problem is that I can only see maybe 3/4ths of the screen. I have fiddled with my screen resolution and followed the troubleshooting steps above, and no dice. . .

Really hoping to get some help as me and my friends lan WWP every week and I need to be ready to kick some ass.

can you describe the problem in detail? can you make a video or do screenshots to show what you mean?

huh, Android? does that mean your notebook has ARM (I havent heard about android for Intel CPUs but yea, I never actually touched any android lol)? in that case you're very unlucky as you'd have to do the whole intel CPU emulation, not to mention the windows OS.

Deadline for the latest contest is Sunday, July 7 (till 23:59 gmt)

Quote from: Rogi on June 28, 2013, 08:54 AMnote: i dint catch timeout error this time, but host didnt work.

host didnt work --- you didnt get into the lobby? or just no one joined?