ansys / ansys/Visual-Interactive-Simulation-Object-Renderer

Annotations / Notes

Ouverte
#74 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub
functional
Langage dominant
Python
Étoiles
0
Forks
0
Merge moyen
1 j 10 h
PR mergées (30 j)
37

Description

### User Story Description

As a user, I want to add annotations or notes to the 3D model by selecting a location and entering text in an input window, so that I can keep track of observations or comments directly on the model.

AVZ currently doesn't support this.

Please note in implementing this that there are 2 types of annotations that can be done: annotations that are located at XY positions in the rendering window, and annotations that are located at a set (X,Y,Z) geometrical space. The first ones stay in the same place when the user rotates / pans the model. The second type moves together with the model. The second type is more important for this user case. But still we need to have a way for the user to easily differentiate between them when creating and interacting with them.

A UX design for this feature can be found here:

https://www.figma.com/design/Hv5VN8vKsVNSueAWf4xo6i/AIEP?node-id=1117-5512&p=f&t=uP75aPtVN3hCAE17-0

### Acceptance Criteria

Open a session of VISOR.
The user can create an annotation set at a fixed X,Y location. When moving the model, the annotation stays at the same screen location.
Now create a second annotation set at a fixed (X,Y,Z) location. When moving the model, the annotation moves with the model itself.

Save a state file. Load a new session of VISOR. Load that state file. The annotations reappear with the same characteristics.

### Additional Links

_No response_

### Requires new or update to third party ? If "yes" add the name(s) and the version(s) of the Third Party Software.

No

### Name and Version for Third Parties

_No response_

Guide de contribution

Ouvrir le guide de contribution

Piste de recherche

Commencez par examiner la conception UX Figma liée et suivre les flux de rendu, de session et de fichier d’état de VISOR. Le travail est considéré comme terminé lorsque les utilisateurs peuvent créer des annotations textuelles fixes à l’écran et fixes au modèle, les distinguer pendant l’interaction et préserver leurs caractéristiques lors de l’enregistrement et du chargement d’un fichier d’état.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
python
Domaine
computer-graphics, frontend
Type d'issue
Fonctionnalité
Difficulté
5/5
Temps estimé
Plus d'une semaine
Activité
Active
Clarté
Plutôt claire
Accessibilité débutants
45/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.