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

Selecting nodes for the first time after project opening is almost always leaving one node unselected #6488

Closed
2 tasks
sylwiabr opened this issue May 1, 2023 · 4 comments
Assignees
Labels
--bug Type: bug d-unknown Difficulty: unable to estimate difficulty p-lowest Should be completed at some point p-medium Should be completed in the next few sprints

Comments

@sylwiabr
Copy link
Member

sylwiabr commented May 1, 2023

Discord username

No response

What type of issue is this?

Intermittent – Occurring irregularly

Is this issue blocking you from using Enso?

  • Yes, I can't use Enso because of this issue.

Is this a regression?

  • Yes, previous version of Enso did not have this issue.

What issue are you facing?

selecting_nodes.mov

Expected behaviour

Nodes in selecting area should be selected

How we can reproduce it?

No response

Screenshots or screencasts

No response

Enso Version

develop @ 6b0c682

Browser or standalone distribution

Standalone distribution

Browser Version or standalone distribution

Standalone

Operating System

MacOS

Operating System Version

No response

Hardware you are using

No response

@hubertp
Copy link
Collaborator

hubertp commented May 2, 2023

Isn't this because it does the re-sizing of nodes while it is loading the possible values?

@hubertp hubertp added the -gui label May 2, 2023
@farmaazon farmaazon added this to the Beta Release milestone May 2, 2023
@vitvakatu vitvakatu changed the title Selecting nodes for the first time after is almost always leaving one node unselected Selecting nodes for the first time after project opening is almost always leaving one node unselected May 3, 2023
@vitvakatu
Copy link
Contributor

It's a bit annoying to reproduce, but I had the best chance by following the same actions as in the video: having one node far to the right and selecting from the bottom right to the top left.

It doesn't look to be caused by node positions or size changes – after all, nodes don't move when we add placeholders and widgets. We only increase their width.

It is worth checking this issue after #6487, as it might be connected.

@vitvakatu vitvakatu added d-unknown Difficulty: unable to estimate difficulty p-low Low priority and removed triage labels May 3, 2023
@farmaazon farmaazon moved this from ❓New to 📤 Backlog in Issues Board May 10, 2023
@sylwiabr sylwiabr added p-medium Should be completed in the next few sprints and removed p-low Low priority labels Aug 2, 2023
@jdunkerley jdunkerley removed this from the Beta Release milestone Aug 31, 2023
@jdunkerley jdunkerley added the p-lowest Should be completed at some point label Aug 31, 2023
@jdunkerley
Copy link
Member

Assumed will be fixed as part of the new IDE work.

@farmaazon
Copy link
Contributor

Not reproduced in GUI2

@farmaazon farmaazon closed this as not planned Won't fix, can't repro, duplicate, stale Feb 27, 2024
@github-project-automation github-project-automation bot moved this from 📤 Backlog to 🟢 Accepted in Issues Board Feb 27, 2024
@farmaazon farmaazon moved this from 🟢 Accepted to 🗄️ Archived in Issues Board May 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
--bug Type: bug d-unknown Difficulty: unable to estimate difficulty p-lowest Should be completed at some point p-medium Should be completed in the next few sprints
Projects
Archived in project
Development

No branches or pull requests

5 participants