Show whole topic
Oct 09, 2016 10:35 pm
Oct 09, 2016 10:35 pm
Subject: Re: 0.2.9 commentary
Hi mdooligan,
thank you very much for the feedback
Of course this would be great! Nevertheless I think it would make sense to open some issues on the bug tracker for your points.
That could be useful features. Please create 2 issues for it.
That will be fixed by the current work on the game logic. Savegame handling has been rewritten completely.
Right, please create an issue for that.
Is this really necessary? Sounds like a trivial detail for me.
Correct. There it already an issue on our tracker: https://git.maxr.org/maxr/maxr/issues/477
Yes, would be nice to have all keys configurable. Please create an issue
Is this really important?
Of course it would technically be possible...
I haven't observed something like this yet. Can't see anything suspect in the code. So we need more details when this happens to be able to fix this.
Yes, we have an open issue in the tracker for fixing the high CPU load in menus.
Did we change the behaviour? I can't remember how it was before. But don't blank the background in dialogs and menus that are smaller than the screen resolution is a valid point. --> Issue 
Hi mdooligan,
thank you very much for the feedback
Quote:
I'll try to offer patches for the ones I can, as I get around to them.
Of course this would be great! Nevertheless I think it would make sense to open some issues on the bug tracker for your points.
Quote:
- option "Click to Scroll" which stops the screen scrolling when the mouse hits the screen edge.
- option to "Invert mouse zoom", a common option in all programs that use the mouse wheel to zoom the way MAXR does. BTW it absolutely great that the zoom targets the mouse cursor.
That could be useful features. Please create 2 issues for it.
Quote:
- Build paths for engineers and constructors are not saved, or are not restored correctly.
That will be fixed by the current work on the game logic. Savegame handling has been rewritten completely.
Quote:
- HOME, END, UP, DOWN, PAGEUP, PAGEDOWN need to work in the build menus. Perhaps DELETE too. One of the dialogs still doesn't have ESCAPE/ENTER working yet.
Right, please create an issue for that.
Quote:
- The original had the term "exploding" for the description in the unitVideo/unitDetails widget (top left) after a unit had been hit.
Is this really necessary? Sounds like a trivial detail for me.
Quote:
- Mobile units had the menu option "Enter" as the corresponding action for "Load" in the Depot/Hangar/etc, so you can tell a unit to Enter the depot, in addition to requesting the depot to Load the unit.
Correct. There it already an issue on our tracker: https://git.maxr.org/maxr/maxr/issues/477
Quote:
- Get the window positioning hotkeys [ALT]F5-F8 into keys.xml so they can be changed. All of the ALT-F keys are scooped by my window manager.
Yes, would be nice to have all keys configurable. Please create an issue
Quote:
- Date format in the saved games. I like YYYY-MM-DD, but at least it's not MM-DD-YY. Is it possible to put the format string into maxr.xml so it can be suited to user? (and not argued over until end of time:)
Is this really important?
Of course it would technically be possible...Quote:
- occasionally unitNext ignores an engineer or constructor who is just finished building. I'm not yet sure why this is. Maybe its movement was exactly 0 when it started building? That's just a guess.
I haven't observed something like this yet. Can't see anything suspect in the code. So we need more details when this happens to be able to fix this.
Quote:
In 0.2.8, the files menu was like PAUSE, the game went into lazy idle and the CPU settled down. In order to PAUSE in 0.2.9, I have to suspend the process (CTRL-Z).
Yes, we have an open issue in the tracker for fixing the high CPU load in menus.
Quote:
Also I liked it better when the files menu came up over top of the main screen like a dialog. Now it blacks the main screen out. I prefer the previous behavior.
Did we change the behaviour?
I can't remember how it was before. But don't blank the background in dialogs and menus that are smaller than the screen resolution is a valid point. --> Issue