Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[NEW-FEATURE] Improve Button Behavior for Pneumatic Piston Movements #747

Closed
mhareznik opened this issue Oct 1, 2024 · 2 comments · Fixed by #758
Closed

[NEW-FEATURE] Improve Button Behavior for Pneumatic Piston Movements #747

mhareznik opened this issue Oct 1, 2024 · 2 comments · Fixed by #758
Assignees

Comments

@mhareznik
Copy link
Collaborator

Currently, the control buttons for the pneumatic pistons TcoCylinder are enabled even when movement to home or work positions is suspended. This can cause confusion for users.
When the piston movement is suspended (for example, due to an safety condition), all related buttons (e.g., "Move to Home," "Move to Work") should also be disabled until the conditions for movement are met.

@peterbarancek
Copy link
Collaborator

/cib

Copy link
Contributor

github-actions bot commented Dec 2, 2024

github-actions bot added a commit that referenced this issue Dec 2, 2024
peterbarancek added a commit that referenced this issue Dec 3, 2024
…758)

* Create draft PR for #747

* ***********TcoCore********
*service view  of generic TcoComponent ,Details  will be expanded by default if IsExpaded is selected
**********TcoPneumatics********
+signalisation  that movement is disabled by suspend method
*  MoveHomeTask automatically restores the opposite task, MoveWorkTask. This principle works in reverse as well

* +resources

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: peterbarancek <62284244+peterbarancek@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants