Minor ease of use suggestions
Posted: 12 Sep 2020, 04:51
Problem: Selecting track or roads within the boundaries of a large tree area can be difficult... you tend to select the tree instead of the track because it's bounding box is large.
Suggestion: Display only objects whose StaticLevelDetail() value is less than or equal whatever value the user sets. Whenever the value changes update display per the new value. This way whatever objects were blocking the access can be temporarily hidden. Default is 10, range 0-10.
Problem: If multiple editing sessions are recorded in the same log file it's hard to find the end of one / start of another.
Suggestion: Either create a new log file with each session where the name includes some sort of time stamp or insert into the existing log file some strings that say something like *** Begin editing session YYYY/MM/DD/HH/MM ***.
Problem: The world object marker is useful when first laying roads or tracks but if you have to return to an area and rework something there is no t way to know where the placement point end is located.
Suggestion: Dynamically change the color or brightness of the world object marker when its object has been selected so the user knows that object marker is for the selected object.
Problem: The color used for a patch boundary is the same (or almost the same) as the color for the path lines above roads which can suggest there is a road shape just below the terrain.
Suggestion: Change the color of the patch boundary lines so it is unique.
Suggestion: Display only objects whose StaticLevelDetail() value is less than or equal whatever value the user sets. Whenever the value changes update display per the new value. This way whatever objects were blocking the access can be temporarily hidden. Default is 10, range 0-10.
Problem: If multiple editing sessions are recorded in the same log file it's hard to find the end of one / start of another.
Suggestion: Either create a new log file with each session where the name includes some sort of time stamp or insert into the existing log file some strings that say something like *** Begin editing session YYYY/MM/DD/HH/MM ***.
Problem: The world object marker is useful when first laying roads or tracks but if you have to return to an area and rework something there is no t way to know where the placement point end is located.
Suggestion: Dynamically change the color or brightness of the world object marker when its object has been selected so the user knows that object marker is for the selected object.
Problem: The color used for a patch boundary is the same (or almost the same) as the color for the path lines above roads which can suggest there is a road shape just below the terrain.
Suggestion: Change the color of the patch boundary lines so it is unique.