Screen centering/cycling around map UI idea
-
re: flags+highlight button
Highlight and flags are available during all turn phases, it makes sense to have those buttons located elsewhere. Where, I'm not sure. The buttons are included because we have hotkeys, if we remove the hotkeys, we can remove the buttons.re: wake-all
@Frostion the wake-all makes sense, I've been working through a stack of items, hopefully will have it soon.Re: sun/moon
@Cernel does raise a good point that sun/moon are opposites and one would expect for the two buttons to have related but opposite functions. They do not. It seems unlikely we'll find a better analogy/terminology other than sleep. Things like "guard", "sentry", "station", etc.. have all been suggested and we've fallen a bit flat for any good terms that do not implicitly convey a benefit nor good icons to represent them. We don't have to find something perfect, but something that can be learned relatively easily and is also not a super-far fetched term that nobody would want to use when talking.re: centering+highlight
I'm opposed to centering that also highlights all moveable. The idea is we have a 'current' selection that changes as units are moved, skipped or put to sleep. Centering is meant to highlight that unit and show where they are on the board. IE: you scroll around on the map and then lose track of where that current unit it is. -
Looks like we have three outstanding issues:
-
button sizing and avoiding cut-off: I'm working on this..
-
sun+moon icon / sleep terminology:
Perhaps "station" could work as a term. The shield icon proposed earlier would work. I'm wondering if a 'fort' icon (ie: a building) would maybe work better, eg: https://thenounproject.com/term/fort/2826313/, https://thenounproject.com/term/castle/1697643/. Then IMO the alarm icon plays nicely as when units are stationed, they go into their fort, hang out, then when the alarm is clicked they wake up and are active. @Frostion, given you've been making the icons, I'm curious what you think would work best for an icon, whether a guard shield, a fort image, or something else. @Cernel , would "station" be a seemingly acceptable term? -
Highlight+flags button positioning:
without further better ideas, the unit scroller will be their home for now. Are there any better ideas of how to incorporate those two buttons into the UI?
-
-
I think it should be on the turn player only. When I'm playing with someone (or watching a game) I think I should not be jumping around as he centres on unmoved units territories. That felt really strange and random. I think I would not even had an idea about wtf was happening if I didn't know about this feature.
-
And every time I hit space bar when chatting I jump around too...
-
@Cernel Probably never mind on this one. I guess I assumed he was using the scroller and I was seeing that, but now I think that was maybe happening because I was typing. Anyways, now typing in chat causes the scroller and the hotkeys to activate, which is very bad.
-
@Cernel Chat interfering with keybindings was: https://github.com/triplea-game/triplea/issues/5286, it's been fixed in the last couple days.
-
Updates:
button sizing and avoiding cut-off: I'm working on this..
I think it's about there. The 32x32 images are still an option, but the unit scroller buttons would look a lot less nice.
Otherwise, the unit scroller was made more narrow, to get to the last mile, a 250px min was added to the action panel. Here is a before/after (please note that even the unit history has trouble dealing with narrow mini-map, it also cut-off and has scrollbars in the before):
sun+moon icon / sleep terminology:
There's been no feedback on the 'station' suggestion. Going with that for now. We can go back to 'sleep', but we'd have to reconcile the iconography.
-
@LaFayette Maybe there should also be a "surrender" button, for ending the game by surrender?
I already said it, but just for the record, I like narrow minimaps, like the one of Napoleonic Empires, as I don't feel I need any more minimum wideness (and I can temporarily increase it for reading Notes or the stats), while I like having board view and I also don't like the fact of having a bar only on one side, as that factually moves the centre of the screen out of its place (I would actually prefer having two bars of the same size on both sides of the screen all the time). As a mapmaker, generally I go for 200 pixels wide minimaps.
-
@LaFayette I'd prefer sleep over station.
-
Just for the sake of trying to end this conversation... how about this...
-
@redrum said in Screen centering/cycling around map UI idea:
@LaFayette I'd prefer sleep over station.
I totally agree. It would be much more intuitive.
Even though soldiers are not given orders to "sleep" or "wake up" in real life wars or battles, I think they are better generic terms when it comes to units in a game. Hence why other games also use it. I think the last thing we should go for is realistic orders/terms just to make them fit modern infantry, as a unit in TripleA can be so many other things then modern infantry. Units can be anything movable already found in TripleA maps.
Basically we just want a term that makes units go inactive and then go active again. That's why "sleep" and "wake up" seems to be the best pick... If we would not use the terms "active" and "inactive".
If the real problem here actually is the sun symbol, in this context, not representing something opposite the moon/zzz symbol, then we could just find/make a new highlight symbol? Maybe a light bulb? Like "notice me!" being said with a light bulb?
-
Terminology
@Cernel had a lot of points against the sleep terminology. Civ uses 'sentry', and I suppose we've ruled that out. 'Station' being a real world term, "A garrison is stationed in the city" is a positive. I'm not necessarily going for military realism, but we want to create analogies and mappings for concepts to be made more obvious, using a real term helps that.
For example: "3 druids and 2 bears are asleep in Gondor". "3 druids and 2 bears are stationed in Gondor". I think 'station' might actually be a better fitting term in the more generic sense. The definition of the word 'station' fits what we want really well:
station 4. the place where someone or something stands or is placed on military or other duty.
I'm really concerned we are stuck in our initial positions and have hit a point of bikeshedding. Let's put a pin in the terminology for a few days. Please everyone play test the new buttons, try to get used to the new terminology, and let's see if we all still feel the same after a few days.
Spacing
@Cernel I agree more space for the map is better. Though, does 30px really make a difference to you? Does the unit history getting cut-off not bother you?
Can we have more opinions on this as well. I'm not a fan of the gap between the mini-map and the right hand edge. I also think though that the minimap size was never made standard and the Napoleonic Wars is an anomaly and was just made too small. The unit history getting cut-off looks bad IMO.
If we seek to make the unit scroller buttons even more narrow, they do not look as good. At this point I think the right answer is to make the minimap slightly larger on that one map. Trading the aesthetic of the unit scroller controls to not look good on every map is a bad trade-off IMO compared to fixing the one map where the minimap is extra small. The unit history being cut-off is significant, the tabs being put to 3 rows instead of 2 is cluttery, the player table being that narrow makes that unusable without resizing.
Sun Icon
@Frostion indeed, sun+moon being false antonyms was a problem. Looking at it, the 'sun' is not quite right. An artificial light source is probably better representative as we shining a spotlight on the unmoved units. @Frostion if you could propose a light bulb, or a lantern, flashlight, search light, something similar that would make a good icon, that would be really appreciated.
-
@LaFayette If "station", maybe the skip one can be called "stay". So, one would have the stay/station alternative as temporary/definitive.
Maybe @redrum just meant he didn't like the "shield" symbol, not really the term station itself. While I like "station", I have to say the shield symbol is surely less clear than the moon one (coming from somebody doesn't actually like that).
-
@LaFayette OK ... Here is a new version of the set. All icons are 37x37 px, so a bit smaller than 39x39. Here are exmales and the zip.
I also want you to know that, even if we are not in total agreement in regards to all aspects, I think we all agree that this feature is 100% thumps up and great I apreciate the work! Keep it going!
The set is a SET meaning they have all the same treatment and are not as the others I have uploaded before. These are a bit more “sharp” in the outline and less shadow.If you like them different or smaller, like 32x32 then let me know and I will make them.
-
@LaFayette I don't think there should be a minimum, or the minimum should be so small to assure to be purely theorical (like a minimum at 100 pixel wide minimap). Then, the default can be whatever it is preferred generally by the developers, but, after starting the game, one should be able to manually reduce the wideness of the sidebar as low as the minimum fitting the minimap. Once you reduce the space so much that the unit scroller doesn't fit anymore, it should disappear, and there should be an option for having it disappear, as well (if someone prefers not having it, maybe to have more space for action display).
Regarding guessing what the assumed miniMap wideness may be, for a predetermined default wideness we can refer to the history tab, and consider that it would make the most sense for two bars on the left and the right of the screen to be preferably of the same wideness. If I load World War II Classic with 2.0.16492 and click on game/show history, the left side bar is exactly 158 pixels wide. Then taking out 10 pixels on the left and 4 pixels on the right of the smallMap, that would give a smallMap of 144 pixels wide, if you want to have the right bar as wide as what you get default for the left bar.
Based on the above, I would say that the standard wideness of the smallMap, currently, should be 144 pixels, but I realize that this is actually much under any average you may derive by looking at the repository maps.
Since TripleA is in the weird condition of not actually having an official main referring game, an alternative way is looking at the smallMaps of world_war_ii_classic (being the first and default game that ever existed for TripleA), of big_world (having been for many years the default game offered by TripleA), and of the_pact_of_steel (being the fist truly custom yet official game of TripleA and having a mod serving as tutorial for mapmakers). The wideness are the following, in pixels:
world_war_ii_classic: 233
big_world: 243
the_pact_of_steel: 233 -
Thanks for the response
@Cernel have you considered the implication for unit move history and the stats table? A unit move history of 150px might cut-off the first unit moved, let alone cutting off on the second.
Once you reduce the space so much that the unit scroller doesn't fit anymore, it should disappear, and there should be an option for having it disappear
We have a "full-screen" mode, the entire right hand edge can be shrunk. Having just the unit scroller disappear is not trivial. A feature to have the right hand edge disappear independent of the mini-map would seem to serve that goal well.
My biggest concern without having a minimum, focusing "too" much on allocating space for the map, is that the unit history and stats tables suffer. It has been a long running annoyance to have to scale the stats table to be able to see the values. It's a particular problem on WaW where many values go beyond the expected 2 digits and are 3 or 4 digits.
-
As another perspective, the minimap sets a minimum sizing (due to the UI framework). So there is a minimum. We are talking about a mere 15px increase of this minimum.
If we disappear elements that do not fit, it's then a difference of 15 px for when the smallest of minimaps and unit scroller would disappear. In other cases, the minimap would disappear before the unit scroller. It's a bit moot as I don't know/think offhand that could be done cleanly.
We certainly could consider having a similar 'hide' button for the unit scroller. It would require some additional space, which maybe is not a good choice. I certainly would like more opinions and feedback before we demo that.
-
@LaFayette if the behaviour of the skip button, beside skipping, is to move to the same next unit you would move by clicking on the right arrow, then it should better stay right under such arrow. However, since there is not an intuitive reason why the skip button should also have a right/left behaviour, it may be advisable that, after you click it, you keep the territory in the scroller, but with no units in it, so that you have to, then, use the left/right arrow to move to either units group presented beside the one you just skipped or stationed.
Station has also the advantage that you can say "I stationed these units", but you cannot say "I slept these units", but you'll need to say "I put these units to sleep", so the term would be actually "put to sleep", not just "sleep".
-
@Cernel "put to sleep" has connotations : )
It's usually used in animal shelters.Skip does advance to the next unit so that we avoid an "empty unit" selection. If you hold space bar, you can skip all units. It seems clunky if you have to alternate between pressing space and 'n' to do that. Alternatively, every time you press 'space' to skip, you'd need to press 'n' to go to the next unit. It's much nicer to be able to skip and go to next without having to do those as two separate actions. The intended use-case for the 'unit-scroller' is to 'scroll' or 'cycle' through all available units.
-
@LaFayette Then, maybe, to keep it coherent the most, we should not have a left/right couple of specular arrows, but just a right arrow (or whatever is working when you click on skip too), while the other arrow should be absent or only working until getting back to the initial unit group displayed, but not any further "back", and displaying a symbol that hints this is only going back on what previously already displayed.