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

improvement: prevent constant update of scan coordinate preview #63

Merged
merged 1 commit into from
Jan 4, 2025

Conversation

hongquanli
Copy link
Contributor

before this (1) set_live_scan_coordinates will be called even if the stage is not moving (2) set_live_scan_coordinates can happen too frequently - problematic for big scan area coverage

before this (1) set_live_scan_coordinates will be called even if
the stage is not moving (2) set_live_scan_coordinates can happen
too frequently - problematic for big scan area coverage
@hongquanli hongquanli merged commit 6e1cf04 into master Jan 4, 2025
3 checks passed
@hongquanli hongquanli changed the title prevent constant update of scan coordinate preview improvement: prevent constant update of scan coordinate preview Jan 4, 2025
@@ -3074,6 +3074,12 @@ def __init__(
self.eta_seconds = 0
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I checked, and we only connect MoveUpdater.position_after_move to update_live_coordinates. It seems like if the position_after_move signal is correct (it only emits after the completion of a move), this might have worked. Did you check if it's working as expected?

Also, if it is working as expected, and we also want a "position_after_move_and_half_hz" or something, we could add that signal to the MovementUpdater. Then the logic for it will be isolated to MovementUpdater, and any other widget that needs a similar signal doesn't need to replicate the logic.

beniroquai pushed a commit to beniroquai/octopi-research that referenced this pull request Jan 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants