[Bug T3D 1.1 BETA 1] Edit Mode Object Selection Inconsistencies Bugs - LOGGED
by Caylo Gypsyblood · in Torque 3D Professional · 05/30/2010 (12:04 pm) · 2 replies
Build: T3D 1.1 BETA 1
Platform: all
Target: Editors
Issues:
The River Object may be selected and moved, while NOT in River Editor mode, but NOT modified.
The MeshRoad Object may be selected and moved while NOT in Mesh Road Editor mode, but NOT modified.
The Decal Road object CAN NOT be modified in any way unless in Road Editor mode.
_Reason this is a bug:
It is seldom desirable to further move the FULL position of these object types once they are placed and edited into the 'world'. It is a time consuming hassle to mass select anything near these types of object as often these 'sub edit mode' objects are also selected and unexpectedly transformed along with the mass selected objects. This is not a logical behavior.
One would expect a selection style continuity between these similar object types. Inconsistencies because it is required to be IN that object type specific sub-edit mode to place and modify said object type in the first place, specific sub-edit mode should ALSO be required to transform the object.
Issues:
The {drop type} Decal object CAN NOT be modified in any way unless in Decal Editor mode.
_Reason this is a bug:
This type of object should be selectable and movable when in normal Object Editor mode, it is VERY often desirable to further position a {drop type}Decal object once it have been created. It is not logical that i should treat this type of object differently then any other ambient in-game-level detail.
Steps to Repeat: NA
Link to Console Log: NA
Suggested Fix:
It would be logical to automatically switch to a sub edit mode when a 'system generated' object is selected, and disregard the 'system generated object' when other object types are also/multi selected.
Thank you
EDIT: reformat to fit 'new' bug reporting system(I hope..)
Platform: all
Target: Editors
Issues:
The River Object may be selected and moved, while NOT in River Editor mode, but NOT modified.
The MeshRoad Object may be selected and moved while NOT in Mesh Road Editor mode, but NOT modified.
The Decal Road object CAN NOT be modified in any way unless in Road Editor mode.
_Reason this is a bug:
It is seldom desirable to further move the FULL position of these object types once they are placed and edited into the 'world'. It is a time consuming hassle to mass select anything near these types of object as often these 'sub edit mode' objects are also selected and unexpectedly transformed along with the mass selected objects. This is not a logical behavior.
One would expect a selection style continuity between these similar object types. Inconsistencies because it is required to be IN that object type specific sub-edit mode to place and modify said object type in the first place, specific sub-edit mode should ALSO be required to transform the object.
Issues:
The {drop type} Decal object CAN NOT be modified in any way unless in Decal Editor mode.
_Reason this is a bug:
This type of object should be selectable and movable when in normal Object Editor mode, it is VERY often desirable to further position a {drop type}Decal object once it have been created. It is not logical that i should treat this type of object differently then any other ambient in-game-level detail.
Steps to Repeat: NA
Link to Console Log: NA
Suggested Fix:
It would be logical to automatically switch to a sub edit mode when a 'system generated' object is selected, and disregard the 'system generated object' when other object types are also/multi selected.
Thank you
EDIT: reformat to fit 'new' bug reporting system(I hope..)
Associate Michael Hall
Distracted...
Bugs?
Maybe not technically, but I'd have to agree with the sentiments expressed here - so definitely a quality assurance issue.
Consistent behavior across these types of similar objects/systems would be more desirable, as well as professional. I can understand old legacy code exhibiting such deviations -- what with the scores of people who added, modified, and removed code over the years. But, these new objects/systems are new and were all introduced in such a short time period that similitude and consistency in operation should have been logical and automatic.