Topic: Add UI buttons for changing game speed
MostlyHarmless Topic Opener |
Posted at: 2017-07-09, 12:48
I would like to play Widelands on my Microsoft Surface Pro 3 and only use the pen on the touch screen. Everything else seemed to work very well with the pen (left click, right click and scrolling with the right click), but I was not able to change the game speed. Even the on-screen keyboard is missing the Page Up and Page Down keys. If there were UI buttons for changing the game speed, I could play the game without a keyboard. Unless you want to get very creative, the icons could be the familiar ones from a VCR: << >> Ofcourse the most awesome thing would be to fully support the touch controls for scrolling and zooming, but even then the game speed needs to be changed somehow and, I think, clear UI buttons is the best way to do it. PS. Please let me know, if there are other crucial hotkeys I shoud be using, which are not available on the UI. I haven't played the game much yet and might be missing something. Top Quote |
kaputtnik |
Posted at: 2017-07-09, 15:23
Hi MostlyHarmless and welcome to our forums All hotkeys are explained if you open the Tribal Encyclopedia (Question mark on the bottom menu) and click on "Controls". How do hotkey combinations, e.g. CTRL + Click on a flag, work on the surface? Or Saving positions with CTRL+Number? The Problem i see with the game speed buttons: Where to place them. Any suggestions? Fight simulator for Widelands: |
MostlyHarmless Topic Opener |
Posted at: 2017-07-10, 19:59
Thanks kaputtnik, and thanks for sorting out the registeration issue. It seems that I have been playing like a peasant without using saved positions or ctrl-clicking flags. Here are my suggestions to solve these: 2) CTRL + click to build roads with flags: So the two issues you brought up do have some kind of work arounds, but for controlling game speed there is nothing else than using the keyboard. I would be extremely happy, if all these features would be usable with the pen on the Surface Pro. Maybe as I suggested or maybe someone else has even better ideas. Edited: 2017-07-10, 20:39
Top Quote |
kaputtnik |
Posted at: 2017-07-10, 20:49
I think your solutions are maybe better for a special version of widelands. Maybe one which fits also for cellphones? Another idea: We currently do not have any doubleclick actions. Maybe this is way to solve some of the problems with hotkey combinations? E.g. when roadbuilding mode is activated, double clicking on a flag places the road and automatically adds flags. Fight simulator for Widelands: |
MostlyHarmless Topic Opener |
Posted at: 2017-07-10, 21:43
Yes, double-clicking sounds good and can be done with a Surface pen. Also the devs seem to be adding the reset zoom button, so the door seems to be wide open for adding more buttons to UI. Otherwise reset zoom would be only a hotkey as well. Top Quote |
Ex-Member |
Posted at: 2017-07-11, 09:52
My 2 cents on this. I do not use savegame on any dame I play, if I screw up and die accept it and start again.. I would not like to lose ant screen estate to more buttons. I am not sure why there is a reset zoom button, it is superfluous even thogh I am constantly zooming in and out I never use it. As for the game speed, I usually set it at the begining and never touch it again, changing economy settings is much more prominent. This does seem to be a special user case, as kaputnik says, perhaps there is a case for several UI setups for special needs? The only thing is that someone with the device would need to write the code and debug it. Top Quote |
GunChleoc |
Posted at: 2017-07-11, 11:04
I am planning a redesign of the bottom toolbar anyway, but I'm still busy fixing the game setup screens, so it might not make it into Build 20. What I have in mind is to use our new capability of drop-down menus to get rid of the permanent little menu windows that we get at the moment (e.g. for game options and statistics). I also want to move the census and statistics off the flag menu and into the main toolbar - we could have a "View" menu there with census, statistics, building plot and zoom options. This way, we will save space while still having everything accessible. Game speed will be awkward as a drop-down menu, but we could have a button-accessible window. Those who don't need it can then keep it closed to save screen space. Busy indexing nil values Top Quote |
MostlyHarmless Topic Opener |
Posted at: 2017-07-13, 15:39
Hi Tinker. Thanks for your feedback and I fully get the idea of a lean and minimal UI, but in my opinion the speed buttons are needed.. Not everyone play the same way you do. I tend to play on slow and then increase the speed for a while, if there's nothing to do. Maybe the game will be a tiny bit more accessible to new users when useful functionalities are visible on the screen and not hidden behind a hotkey. You know kids these days; they don't like to read manuals No special device is needed for coding or debugging. If the button is clickable with a mouse, I can click it with the Surface Pen. Thanks GunChleoc! I saw some of your ideas and pictures in another thread and the drop-down (-up?) menus seems to be the golden road here. Could there be an option for using the drop-down menus or spreading all those buttons to the bottom of the screen? Or maybe a right-click on the drop-down menu would keep the menu open until right-clicked again? If left-clicked, the menu will open, left-click on a button would do the desired function (reset zoom, change speed, open the economy settings...) and then close the drop-down menu. That way I can clutter my screen with all the buttons I like and others can keep the menus closed, if they want. Or is this what you meant by "button-accessible window"? If this doesn't make it into 20, then when would 21 be stable enough to play? It looked like there was 3 years between 18 and 19, so will it take 6 years? Top Quote |
GunChleoc |
Posted at: 2017-07-14, 09:16
It all depends on how many people are around to code and review stuff in their spare time. I currently have a lot of branches stuck in code review... Busy indexing nil values Top Quote |