Feedback regarding the scene navigation and management (in the online authoring tool):
[ ] Creating a new scene → importing a Lab model into the scene → while in 2d view → The room is initially shown at a small scale and the user can see the available gizmos: move, rotate, delete. As the user zooms in, it would be nice if the gizmos were scaling in such a way that they are always visible (their size defined in relation to the screen size, as opposed to having a real - world size). Otherwise the user needs to zoom out in order to perform these operations and zoom in again.
[ ] The move gizmo (arrow pointing to the right) could be a cross (indicating that it can move in all directions) instead of an arrow. The arrow pointing to the right can be a bit confusing as to its actual functionality.
[ ] It would also be helpful if – when an object is selected - there was some text (together with the gizmos), stating the selected object that those gizmos refer to (e.g. the camera, or the room)
[ ] When exiting the VIEW (looking through the camera), the scene's view scale changes to its default value. This can be a bit frustrating, because one has to zoom in again in order to get to the previous state. Perhaps store the previous state?
[ ] Same goes for when changing between 2d and 3d view...
[ ] Rotate view does not seem to work as stated in the tutorial “Scenario1_june2018.pdf” - by left - clicking. Instead of that, it works with the middle mouse button. Perhaps correct the tutorial - description?
[ ] When trying to move the scene (by right clicking), if the right click is on top of the camera, an error message appears ("do not right click on camera") and then the right click button is stuck on the pressed state (meaning that just moving the mouse moves the scene) until some button is pressed again.
[ ] The mid - click (scene rotation) is a bit too responsive. It is difficult to bring the scene to a specific angle. Rotation happens too fast and also has an 'elasticity', continuing to rotate after the mouse stops moving, making it even more difficult to adjust.
[ ] The avatar's movement is kind of weird: moving the mouse to the right rotates the avatar to the left and vice versa. This is kind of counterintuitive, in my opinion.
[ ] Exiting the Avatar mode also sets the 3d view's scale to its initial potition. Have to zoom in again, frustrating.
Other observations:
[ ] In the scene editor, at the “transform panel” (top – left), there are three tabs: Move(T), Rotate (Y) and Scale(U). The Rotate tab's text is overflowing, causing the tab to hover over the content, below. This might be a css / javascript issue?
[ ] At the compile step: After the compilation has finished, a message to download the zip file appears. However, the Proceed button is still active. The user may be confused and press Proceed again, in which case the application just compiles again. Perhaps disable the proceed button, after the compilation is done?
In the compiled application:
[ ] When the application is ran in windowed mode, when using the mouse to rotate the avatar's view, there is a chance that the mouse exits the application's window, pointing to the desktop behind it. If the user clicks at this point, the application loses focus.
[ ] In the molecule editing view (where the user has to drag and drop the correct atoms to create a molecule, sometimes the correct atom will not fit into place, at some specific rotation. There might be an issue with the collision – detection?
Feedback regarding the scene navigation and management (in the online authoring tool):
[ ] Creating a new scene → importing a Lab model into the scene → while in 2d view → The room is initially shown at a small scale and the user can see the available gizmos: move, rotate, delete. As the user zooms in, it would be nice if the gizmos were scaling in such a way that they are always visible (their size defined in relation to the screen size, as opposed to having a real - world size). Otherwise the user needs to zoom out in order to perform these operations and zoom in again.
[ ] The move gizmo (arrow pointing to the right) could be a cross (indicating that it can move in all directions) instead of an arrow. The arrow pointing to the right can be a bit confusing as to its actual functionality.
[ ] It would also be helpful if – when an object is selected - there was some text (together with the gizmos), stating the selected object that those gizmos refer to (e.g. the camera, or the room)
[ ] When exiting the VIEW (looking through the camera), the scene's view scale changes to its default value. This can be a bit frustrating, because one has to zoom in again in order to get to the previous state. Perhaps store the previous state?
[ ] Same goes for when changing between 2d and 3d view...
[ ] Rotate view does not seem to work as stated in the tutorial “Scenario1_june2018.pdf” - by left - clicking. Instead of that, it works with the middle mouse button. Perhaps correct the tutorial - description?
[ ] When trying to move the scene (by right clicking), if the right click is on top of the camera, an error message appears ("do not right click on camera") and then the right click button is stuck on the pressed state (meaning that just moving the mouse moves the scene) until some button is pressed again.
[ ] The mid - click (scene rotation) is a bit too responsive. It is difficult to bring the scene to a specific angle. Rotation happens too fast and also has an 'elasticity', continuing to rotate after the mouse stops moving, making it even more difficult to adjust.
[ ] The avatar's movement is kind of weird: moving the mouse to the right rotates the avatar to the left and vice versa. This is kind of counterintuitive, in my opinion.
[ ] Exiting the Avatar mode also sets the 3d view's scale to its initial potition. Have to zoom in again, frustrating.
Other observations:
[ ] In the scene editor, at the “transform panel” (top – left), there are three tabs: Move(T), Rotate (Y) and Scale(U). The Rotate tab's text is overflowing, causing the tab to hover over the content, below. This might be a css / javascript issue?
[ ] At the compile step: After the compilation has finished, a message to download the zip file appears. However, the Proceed button is still active. The user may be confused and press Proceed again, in which case the application just compiles again. Perhaps disable the proceed button, after the compilation is done?
In the compiled application:
[ ] When the application is ran in windowed mode, when using the mouse to rotate the avatar's view, there is a chance that the mouse exits the application's window, pointing to the desktop behind it. If the user clicks at this point, the application loses focus.
[ ] In the molecule editing view (where the user has to drag and drop the correct atoms to create a molecule, sometimes the correct atom will not fit into place, at some specific rotation. There might be an issue with the collision – detection?