Summary of plans for UI overhaul.
The 'crown' button that toggles the TM:PE toolbar:
I'd like to see a major overhaul of the toolbar (aka 'main menu'). See: #51 and #21
I think we can provide more functionality with 8 buttons than the current 12 buttons.
Lights button - see: #8
Junctions button - see: #6
Overlays: As there are two applicable, right-click needs to cycle combinations (as applicable, depending on what's enabled on maintenance tab):
Pedestrian button - see: #40
Routing button - see: #41
Speeds tool - see: #84
Vehicles button - see: #42
Parking button - see: #47
I have some enhancement ideas which I'll post in separate issue
Eraser button
I'll create separate issue to describe this, but in summary:
Multi-purpose tool:
- Can delete customisations associated with active tool
- For example, if lane arrows tool is already active, click eraser then click junction to erase the lane arrow/connection customisations for that lane
- When used on its own, shows additional buttons for despawning/clearing traffic, etc
I'll add new milestone with regards to User Interface changes.
Additionally I'm thinking about setting up few projects to group some of issues and easier progress tracking, but I'm not sure its worth time.
I imagine the UI updates will be spread across releases / milestones. It might be worth having a "UI" label or project though...
Simplification of tool / button names:
Lights tool would then become obvious place to toggle traffic lights. Need to ponder how that would work.
Also, if user goes in to Eraser tool (whilst not in another tool), they could Ctrl+Click the other tool buttons to erase stuff associated with them (with confirm dialog to avoid disasters)?
Any chance to have the button embed into the toolbar like some mods (Touch This, Find It) do?
Also, if it hasn't been done already, a way to apply junction restrictions to an entire roundabout at once?
Also, if it hasn't been done already, a way to apply junction restrictions to an entire roundabout at once?
That is not UI but it is something I'd like also. I'll make an issue for it.
@RenaKunisaki We're working on something like that - see #51 - we hope to have a button that adapts to the design of where you drag it (eg. if you drag it over main toolbar strip, it will become a toolbar button).
As for the junction restrictions, we hope to have something like that at some point, but it relies on reliable roundabout detection. It would be better if the roundabout builder mod added the restrictions (I think it already has integration with TMPE but not had chance to test).
As for the junction restrictions, we hope to have something like that at some point, but it relies on reliable roundabout detection. It would be better if the roundabout builder mod added the restrictions (I think it already has integration with TMPE but not had chance to test).
It has TMPE integration, although it sometimes fails like in this video.
In my case, more than roundabouts, I'd want the priority road to have different junction restrictions such as "vehicles enter a blocked junction" for the main road. As for the detection, the one used for priority roads of "Priority signs" appears to be fine, at least, for an initial version.
Hi, I found this thread by accident. My Roundabout Builder mod sure has integration with TMPE, but uses a little cheat to apply the restrictions. After a segment is built, TMPE waits for some time before setting it up, thus I cannot apply the restrictions right away, as they would be removed right after. Thus I added a stopwatch to wait for some time and then apply them, but I am not too happy about it. It would be probably better to wait for a given number of simulation steps because it sometimes happens that the stopwatch goes off too quickly. Anyway, if you have any advice how to integrate it with TMPE better please tell me
@Strdate Let's make another issue and discuss there (i have created #472).
I have some ideas, like there we have an issue regarding an event sending/handling in TM:PE #426 (this is regarding AI but it can be reused for external commands just as well), so if that is ever implemented, you could put an event requesting road restrictions change.
@aubergine10 Regarding the main menu overhaul
Do you reckon is makes a good sense, having a state-machine in the main menu, where clicking a button would change the main menu to a new view with a ◀ button (go back) and new buttons relevant to the current operation mode? Because that is something we can totally do without (large) changes to all existing tools, and improve usability by also exposing new buttons with each tool's own available actions.
Something like (well in this example i imagined ahead what the lane arrows tool would do in the future):
(You can probably see how this is very similar to OSD panel functionality)
@kvakvs I'm not sure. Something does need to change in the top-level UI, but I think the only way to determine best approach is to do some sprints of different ideas.
These are the approaches I can currently think of:
The winner will be whatever "feels" best, but I can't quantify "feel" hence I think we need some sprints to try different approaches.
1 (keep existing) is very similar to 3 (dynamic panel) but they can be combined, so that the top level menu is smaller and is always visible, for allowing you switch the tools. And the space below them would be the context-dependant controls, hints and help?
Iterating on all 4 would take 4x the time though
I think we could likely skip the last one (use vanilla-style build bar) as it takes up too much room.
I still love the idea of the 'flower' menu thing, but how to activate it considering we use right-click already in most tools? Would it only be for top-level tool selection, or/and context options?
For dynamic floating menu, we could possibly add an extra row of context buttons when a tool is active, but it might be confusing for users?
Most helpful comment
Hi, I found this thread by accident. My Roundabout Builder mod sure has integration with TMPE, but uses a little cheat to apply the restrictions. After a segment is built, TMPE waits for some time before setting it up, thus I cannot apply the restrictions right away, as they would be removed right after. Thus I added a stopwatch to wait for some time and then apply them, but I am not too happy about it. It would be probably better to wait for a given number of simulation steps because it sometimes happens that the stopwatch goes off too quickly. Anyway, if you have any advice how to integrate it with TMPE better please tell me