KitwareMedical / KitwareMedical/SlicerLayerDisplayableManager

Add support for throttling and debouncing

Open
#6 0 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
C++
Stars
4
Forks
2
PR merge metrics
No merged PRs in 30d

Description

Related to #5

When updating the display, it may be interesting to not update the display for all object updates.
Implementing a debouncing or throttling would improve the responsiveness of some Pipelines in conjunction with threaded updates.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reading related issue #5 and the repository description to understand the displayable manager architecture and threaded update context. Determine whether throttling or debouncing is appropriate for display updates, and define completion by demonstrating improved responsiveness without processing every object update.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
performance
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.