Skip to content

fix(TextActor): add support for property change#3447

Open
daker wants to merge 1 commit intoKitware:masterfrom
daker:fix-textactor
Open

fix(TextActor): add support for property change#3447
daker wants to merge 1 commit intoKitware:masterfrom
daker:fix-textactor

Conversation

@daker
Copy link
Collaborator

@daker daker commented Mar 24, 2026

fixes #3445

Context

Results

Changes

  • Documentation and TypeScript definitions were updated to match those changes

PR and Code Checklist

  • semantic-release commit messages
  • Run npm run reformat to have correctly formatted code

Testing

  • This change adds or fixes unit tests
  • Tested environment:
    • vtk.js:
    • OS:
    • Browser:

@daker daker marked this pull request as ready for review March 24, 2026 23:35
}

if (property) {
model.propertySubscription = property.onModified(() => {
Copy link
Member

Choose a reason for hiding this comment

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

vtk.js philosophy is not so much to "update" itself as a reaction to changes. Instead, it should wait to be rendered to update itself.

@sankhesh what event can trigger a texture refresh ?

@daker daker force-pushed the fix-textactor branch 2 times, most recently from 59528e4 to 4fd7a45 Compare March 25, 2026 17:19

if (property) {
propertySubscription = property.onModified(() => {
if (model.input !== undefined) {
Copy link
Member

Choose a reason for hiding this comment

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

if input was valid and becomes invalid, it should probably clear the texture hence it must be updated.

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.

[Bug] Can't change vtkTextActor color

3 participants