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

Images flickable has performance bug #187

Merged
merged 8 commits into from
Feb 5, 2024
Merged

Images flickable has performance bug #187

merged 8 commits into from
Feb 5, 2024

Conversation

Tayebe79
Copy link
Member

@Tayebe79 Tayebe79 commented Jan 30, 2024

Description

Images flickable has performance bug when all nodes are selected fixed

Fixing #178 , #179

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules

@Tayebe79 Tayebe79 requested a review from l3enQ January 30, 2024 07:29
@Tayebe79 Tayebe79 self-assigned this Jan 30, 2024
Copy link
Contributor

@l3enQ l3enQ left a comment

Choose a reason for hiding this comment

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

should this PR fix both issues? if so please complete this! otherwise move related changes to another branch

Comment on lines 109 to 123
Object.values(nodes).forEach(node => {
selectNode(node);
selectedModel[node._qsUuid] = node;
});

Object.values(links).forEach(link => {
selectLink(link);
selectedModel[link._qsUuid] = link;
})

Object.values(containers).forEach(container => {
selectContainer(container);
selectedModel[container._qsUuid] = container;
})

selectedModelChanged();

}
Copy link
Contributor

Choose a reason for hiding this comment

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

fixing another issue for select all performance! mention in the description!
but it will not fix selecting with marquee performance bug!

Copy link
Contributor

@l3enQ l3enQ left a comment

Choose a reason for hiding this comment

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

@mohsenkondori please check my changes
@HamedMasafi we need to profile it

Copy link
Contributor

@l3enQ l3enQ left a comment

Choose a reason for hiding this comment

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

loading file still is slow! the selection model and addNode method can be optimized for this scenario

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.

3 participants