PRACX v1.10 Release

[Yitzi]

That should depend on the screen resolution you pick on the preferences window, Yitzhak.

Ah, ok.

[Yitzi]

When I disable it via Disabled=1, I get a segfault, and when I don't disable it and it crashes for another reason (e.g. bug-hunting with the next version of my patch) while running Ollydbg, it doesn't switch to Ollydbg (as the original did) or even let me minimize.  (If I reduce the size beforehand it's ok, but it's still annoying.)

[Lord Avalon]

Lord,

I hadn't noticed what the mouse scroll did on the city screen.  I can change it to pass the wheel through when that screen is up.

There is a windows call to set a bounding rectangle for the cursor.  I only have one monitor hooked up, though, I'd be leery of messing with that without being able to test it.

Edit: No scrolling in Design Workshop when you pick weapons etc? Map behind zooms in & out. This is when DW is accessed from base build screen. When DW is accessed directly, scroll to select is row-by-row, rather than everything moves at once.

Edit2: Ooh, this is bad - also in Design Workshop, cannot click on left arrow to move towards obsolete units - map scrolls instead. (Right arrow works.) N.B.: this happens when DW is accessed from base screen. If I go directly into DW, it's OK.

[PlotinusRedux]

Unrelated, GOG decided to prevent alt-tab with sdbinst. The GoGwiki has instructions on how to restore it. I think just using that is a better solution than mapping tab to toggle window.

I didn't even know that bloody thing existed.  http://www.microsoft.com/en-us/download/confirmation.aspx?id=7352 is an app to create them and see all the ones installed.  It looks like the *only* thing in the db's they installed is disabling ALT-TAB.  I'll add an uninstall og them to my the install script of my next release.  I'll probably leave <TAB> alone as a toggle, though--I've gotten used to it now as a way to quickly go to windowed mode then back.

[PlotinusRedux]

When I disable it via Disabled=1, I get a segfault, and when I don't disable it and it crashes for another reason (e.g. bug-hunting with the next version of my patch) while running Ollydbg, it doesn't switch to Ollydbg (as the original did) or even let me minimize.  (If I reduce the size beforehand it's ok, but it's still annoying.)

Fixing the Disabled thing.  Your debug behavior is the exact opposite of mine, though--before my patch, I couldn't get IDA or Visual Studio's debuggers to show over it, after the patch they do.  Maybe fixing the ALT-TAB thing will give me the same behavior you're seeing.  If not, at least Disabled will work.

Did changing the screen resolution on the Pref's window fix the stretching issue you saw?

[PlotinusRedux]

Edit: No scrolling in Design Workshop when you pick weapons etc? Map behind zooms in & out. This is when DW is accessed from base build screen. When DW is accessed directly, scroll to select is row-by-row, rather than everything moves at once.

Edit2: Ooh, this is bad - also in Design Workshop, cannot click on left arrow to move towards obsolete units - map scrolls instead. (Right arrow works.) N.B.: this happens when DW is accessed from base screen. If I go directly into DW, it's OK.

I'm reaching out to Yitzi and Scient to see if one of them has a better method of detecting when a pop-up window is open.  I was using code the game itself used, but apparently it's missing some cases.

[PlotinusRedux]

Yitzi--I've got the Disabled fixed, but even fixing ALT-TAB on my box, all my debuggers pop up over full screen with the patch, where they didn't before the patch--still the exact opposite of what you're seeing with Ollydbg.  At least you'll be able to just disable my patch now when you're doing your work, and of course you can always window it if the patch is on.

I also fixed an issue with the Resource display mode I'd never seen because it only showed up with Optimization on during building, which was only the case for Release builds, whereas I'm always using the Debug builds--I just turned off Optimization for both.  No telling what else that might have affected.

[Yitzi]

When I disable it via Disabled=1, I get a segfault, and when I don't disable it and it crashes for another reason (e.g. bug-hunting with the next version of my patch) while running Ollydbg, it doesn't switch to Ollydbg (as the original did) or even let me minimize.  (If I reduce the size beforehand it's ok, but it's still annoying.)

Fixing the Disabled thing.  Your debug behavior is the exact opposite of mine, though--before my patch, I couldn't get IDA or Visual Studio's debuggers to show over it, after the patch they do.  Maybe fixing the ALT-TAB thing will give me the same behavior you're seeing.  If not, at least Disabled will work.

Did changing the screen resolution on the Pref's window fix the stretching issue you saw?

Yes, it did, though as it said I needed to restart the program.

Edit: No scrolling in Design Workshop when you pick weapons etc? Map behind zooms in & out. This is when DW is accessed from base build screen. When DW is accessed directly, scroll to select is row-by-row, rather than everything moves at once.

Edit2: Ooh, this is bad - also in Design Workshop, cannot click on left arrow to move towards obsolete units - map scrolls instead. (Right arrow works.) N.B.: this happens when DW is accessed from base screen. If I go directly into DW, it's OK.

I'm reaching out to Yitzi and Scient to see if one of them has a better method of detecting when a pop-up window is open.  I was using code the game itself used, but apparently it's missing some cases.

I would probably just put a dummy bit somewhere (I have a few available if you want, and simply enable it when the popup window is opened and disable it when it's closed).

Yitzi--I've got the Disabled fixed, but even fixing ALT-TAB on my box, all my debuggers pop up over full screen with the patch, where they didn't before the patch--still the exact opposite of what you're seeing with Ollydbg.

Did you try it with a crash-causing bug (e.g. segfault)?  When there's no crash, it works fine (but IIRC still doesn't pop up at a breakpoint), but when it hits a segfault it won't let me alt-tab.

[ete]

hmm, I'm getting a bug where while watching the AI play out long turns it jumps to windowed mode and displays a circle instead of mouse. If you click anywhere it gives an error about the program not responding, but you can see the turn going on in the background. My guess is windows things the program is unresponsive during the off-turn, and now has a way to un-fullscreen?

I've attached a save which demonstrates it for me, just hit end turn and wait. If your comp is so fast it does that one before unresponsive hit y for full vision, or I'll dig up a bigger save.

Also, mouse wheel scrolling is now working in a bunch of places! It's a HUGE improvement.

Resource yield displays are still buggy:

Current yield, showing 3 for energy where it should be one (and the bottom box is wrong about it's yield with 'Solar' aka Tidal Harness).

There's also a minor glitch with the zoom on the square below the one selected in scenario editor.


Potential Yield, displaying as if adding a Kelp Farm would bring it to 2, with a kelp square next to it showing that it should give 3. Also wrong in bottom box.



Also this. On current yield rocky squares and altitude squares incorrectly display potential yield instead of current.

[PlotinusRedux]

v1.02 released, should fix the incorrect resource calculations and disable GOG's <ALT-TAB> block on install.  Also Disabled=1 should no longer crash.

I'm still deciding how best to handle falling through to the default mouse wheel handler for windows that have one, per Lord Avalon.

Yitzi--I've seen what you're talking about with the debugger not always popping up over full screen, though that happens to me with or without the patch.  I don't have an idea how to change that yet--I just debug it in windowed mode for the most part.

[TarMinyatur]

If I use the 1366x768 screen mode in PRACX, my terran.exe crashes when I press the left arrow key four times in a row to move the selected tile ('V', left, left, left, left, {crash}). This doesn't happen if I use 1024x768.

I've attached an Ollydbg capture of the access violation. 

[ete]

Scrolling with mouse wheel and zooming with mouse wheel seems to be disabled entirely? It was working with 1.01, but now I've updated it's not working anywhere. And even zooming with keys is not fully functional, it won't let me zoom out past default (though I can zoom in a long way). I don't think I've screwed up preferences again, tried changing a bunch and it's not started working again.

[PlotinusRedux]

Scrolling with mouse wheel and zooming with mouse wheel seems to be disabled entirely? It was working with 1.01, but now I've updated it's not working anywhere. And even zooming with keys is not fully functional, it won't let me zoom out past default (though I can zoom in a long way). I don't think I've screwed up preferences again, tried changing a bunch and it's not started working again.

D'oh, I forgot I disabled it to test some stuff, it's re-enabled now (v1.03).  I knew I was forgetting something.

I'll try to look at the left arrow crash at wide resolution you found in the next few days, Yitzi.

[ete]

The default number of zoom levels is 21 somehow, clicking increase lowers it to 20 which reenables zooming out (with 21 it's impossible to zoom out further than default, but you can still zoom in).

[PlotinusRedux]

The default number of zoom levels is 21 somehow, clicking increase lowers it to 20 which reenables zooming out (with 21 it's impossible to zoom out further than default, but you can still zoom in).

The default should still be 6 (which is really 7)--I just tested it here.  There's an issue with the way I implemented putting 0 zoom in the middle, though--since the game can only handle integer levels of zoom, if the (max_zoom_out/(zoom_levels/2)) < 1, rounding puts two adjacent zoom levels at the same value, which then confuses the code determining the current zoom level.

It generally just occurs with either very small maps (30x30, say) and/or very high # of zoom levels.

I'm going to completely redo that algorithm soon and think through the min/max cases a little better.