User Interface (UI) suggestions

[Fenyő]

Hi!

I haven't seen a UI topic, so i opened it.

I have many suggestions for the UI.

First of all, it would be great to scroll in the Battlescape with the mouse with a left-button hold-down, just like in Transport Tycoon Deluxe, or in OpenTTD!

Actually, i have spent my whole afternoon on inspecting OpenXcom codebase, and i managed to implement this feature.
More information about this is in the development section, HERE.

[Daiky]

I'll have to point you to this:
https://openxcom.org/forum/index.php/topic,189.0.html

the right-button hold down was implemented, it was gone for a while but planned to be added again

[Fenyő]

I'll have to point you to this:
https://openxcom.org/forum/index.php/topic,189.0.html

Why is this topic avoided my eyes??

BTW, i have other UI related ideas, so the topic opening for collecting UI related things is not useless.

[AndO3131]

It's been a while since  last compilation of OpenXcom source code. I'm very glad there's so mouch stuff going on around here. Keep up the good work

My suggestion is about "New battle" feature. When you start new battle, you can make various adjustment: mission, terrain, etc (left click -> next option). It's an excelent idea. I would suggest adding 'right click -> previous option' functionality.

[Fenyő]

It's been a while since  last compilation of OpenXcom source code.

You mean here, on the site?
Maybe you are not aware of the GIT-buids ?

[Fenyő]

Ok.

Next feature suggestion:
Left-Mouse-Scrolling on the MINIMAP!

Actually i've just implemented this.
You can find it in the development section, HERE.

[Fenyő]

I'm wondering if this left-mouse-scroll feature should be implemented to Geoscape also, or should not.
Does it make sense?
What do you think, guys?

[Volutar]

geoscape heavily using caching, and smooth scrolling will lower fps greatly

[Fenyő]

geoscape heavily using caching, and smooth scrolling will lower fps greatly

That's an addition to the difficulties. And Geoscape is not flat, like Battlescape, so its even harder to implement.

So the question is it worth to implement, or no, because not so much benefit the user has from it?

[Volutar]

Actually I think it need to be implemented, though not in software 320x200 mode. OpenGL after 1.0 would be nice.

[mercy]

Yeah, some new planet shading in software mode, maybe a slight atmospheric glow? Or night-lights vanishing on continents as the sun rises.

[Volutar]

No need of realistic things really. Because it's a command-center visualization, not real Earth from outer-space observation. Thus no clouds, no athmosphere, no sun or flares required. It actually will be a visual obstacle.

[Fenyő]

Next suggestion:
Right-click on arrow buttons should mean MAXIMUM/MINIMUM.
Example: on the Research project screen you click on the increase scientists button with the right button of the mouse, and the scientists allocated is set to maximum value, immediately!
Or you click on decrease scientists button with the right button of the mouse, and the scientists allocated is set to 0, immediately!
Imagine this function on the Research Project screen, Manufacture allocation screen (count of engineers, pieces to produce), Craft Equipments screen, Transfer items screen, Buy/Hire screen, Sell/Sack screen!

Yes, I've done it (all of these) again!
You can find it in the development section, HERE.

[sklll]

Wow!
Guys, its the fastest response I have ever seen!
Respect!

But as of original issue with right-button scrolling:
As adding of some movement threshold appears to be a good idea - then we need some criteria to differentiate two user actions (scrolling and cancelling).
I suggest to use the time between MouseDown and MouseUp events in addition to movement threshold.
Cancel action usually takes much less time than scrolling. So some constant in miliseconds can help...

Thus:
1. Cancel action - mouse can be moved slightly, but click must be fast;
2. Scrolling action - all other cases (right-button held or mouse moved greatly).

[Fenyő]

I suggest to use the time between MouseDown and MouseUp events in addition to movement threshold.
Cancel action usually takes much less time than scrolling. So some constant in miliseconds can help...

Hmm, that's an other excellent idea!!