ISISComputingGroup / ISISComputingGroup/IBEX
GUI: Resetting the scripting layout loses the console window potentially
- Lenguaje dominante
- Sin datos de lenguaje
- Estrellas
- 6
- Forks
- 2
- Merge medio
- 16 h 40 min
- PR fusionados (30 d)
- 2
Descripción
As a user, I am experiencing a missing scripting console window which is causing an inability to see what would be in there, or to script anything goign forward.
### How & Where?
- Testing some older tickets I moved the scripting console window, so it was under the blocks.
- Pressing reset layout removed the console from the wrong place, but didn't put it in the right place. It is now missing completely
### Reproducible (Yes/No)?
Yes - as per the How & Where
### Additional Information
Not applicable
# Acceptance Criteria
- [ ] When resetting the layout of the scripting perspective the console returns to the appropriate location
- [ ] If the above is not possible, disable the reset layout button when scripting is the active perspective
# How to Review
Before making a PR...
- _Provide verbose instructions for the reviewer to test that your changes work and fix the issue_
- _Describe if/how you have implemented testing for this issue_
- _Provide screenshots of the feature to help the reviewer if relevant_
_If not applicable, write "Not applicable"_
[comment]: <> (FILL IN BELOW)
> ...
**To the reviewer: Make sure to [update submodules](https://github.com/ISISComputingGroup/ibex_developers_manual/wiki/Git-workflow#reviewing-work-for-the-submodules-of-epics)!**
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Línea de trabajo
Reproduce the issue by moving the scripting console, resetting the scripting perspective layout, and checking whether the console returns. Start by tracing the reset layout button's handling for the scripting perspective; done means the console returns to its appropriate location or the button is disabled there. No file or test is named in the issue.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Área
- desktop
- Tipo de issue
- Error
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 38/100