As a part of this macro-scopic issue, we want to be able to easily add/remove lanes on the outside
Requirements for this task:
Create 4 buttons in the new roadpoint editor panel: Add/remove lane for reverse/forward
Do not worry about the button layout too much, we will improve over time; this is mostly a stepping stone to the 3D widget anyways.
In the meantime, expect to create a row which just reads Lanes: [+][-] || [-][+] where the || could be an icon for double yellow lines for instance.
Maybe we also insert a label in a row above the buttons that reads Reverse and Forward, let's see what fits.
On pressing the according + button, it would add one extra lane to the outside
The according [-] button should be grayed out if ever there are no lanes in that direction (e.g. if there are only forward lanes, the "remove reverse lane" function can't do anything)
There is no limit on the number of times you can press the [+] button.
Lanes are always added (or subtracted) from "the outside", similar logic to how we deal with lane transitions
Automatically trigger regenerating of the according road segments (the one before and after).
Out of scope:
Creating a 3D editor widget, interactive control inside the 3D view (that will be a task after this one)
Affecting more than one roadpoint at a time
Long term reference mockups
Again, per scope above, we're not making a 3D widget right now, and we're only affecting one roadpoint at a time. However this end still is still helpful as a reference:
Then using the controls we have with this task, we'd be able to accomplish the below (again, one road point at a time):
As a part of this macro-scopic issue, we want to be able to easily add/remove lanes on the outside
Requirements for this task:
Lanes: [+][-] || [-][+]where the||could be an icon for double yellow lines for instance.ReverseandForward, let's see what fits.Out of scope:
Long term reference mockups
Again, per scope above, we're not making a 3D widget right now, and we're only affecting one roadpoint at a time. However this end still is still helpful as a reference:
Then using the controls we have with this task, we'd be able to accomplish the below (again, one road point at a time):