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

[4.1.0] Sometimes, objects cannot be selected after slicing and then switching back to 'Prepare' #5880

Closed
rreilink opened this issue Jun 9, 2019 · 14 comments
Labels
Status: Needs Info Needs more information before action can be taken. Status: Stale ⌛ This issue is over a year old. It might be obsolete or just needs a fresh set of eyes Type: Bug The code does not produce the intended behavior.

Comments

@rreilink
Copy link

rreilink commented Jun 9, 2019

Application Version
4.1.0

Platform
macOS

Printer
Ultimaker S5 / Ultimaker 3; occurs with either

Actual Results
Add a part to the build plate. Slice. Switch to 'Preview'. Switch back to 'Prepare'. Click an object. The object cannot be selected. The object can be selected by 'Select All Models' function. note: the bug does not always occur, I have not been able to find out what triggers the bug.

Expected results
Clicking the model should select the model

@rreilink rreilink added the Type: Bug The code does not produce the intended behavior. label Jun 9, 2019
@Ghostkeeper
Copy link
Collaborator

Ghostkeeper commented Jun 10, 2019

It's working fine here. Here is me performing your reproduce steps: http://dulek.net/work/SelectingAfterSlicing.mp4

Maybe MacOS only? I was using Windows. Did I execute your reproduce steps correctly?

@Ghostkeeper Ghostkeeper added the Status: Needs Info Needs more information before action can be taken. label Jun 10, 2019
@rreilink
Copy link
Author

Indeed I am not experiencing this on Windows. There seems to be some region in the viewport that is'not-clickable':

  • Some regions allow selection of the model, others are 'not-clickable'
  • When rotating the view, the same region (referred to screen coordinates) stays 'not-clickable'; i.e. changing the view does allow the model to be selected by moving it out of the viewport.

Is there a way to display or save the selection buffer?

@fieldOfView
Copy link
Collaborator

I have seen something similar on Windows, but could not reliably reproduce it and am often doing "naughty" things with the viewport so I was blaming myself. On Windows you would use renderdoc.org to inspect opengl texturebuffers such as the selectionbuffer.

@Ghostkeeper
Copy link
Collaborator

Ghostkeeper commented Jun 18, 2019

There seems to be some region in the viewport that is'not-clickable'

Yeah we've seen this quite often but never could lay a finger on what's causing it. And the bug is very fleeting. Sometimes it gets fixed by rotating the camera or something. Sometimes not (as we tested).

@no-response
Copy link

no-response bot commented Jun 19, 2020

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

@no-response no-response bot closed this as completed Jun 19, 2020
@Ghostkeeper
Copy link
Collaborator

We haven't been able to reproduce this issue yet. Needs testing on MacOS though, which is difficult to come by since none of our developers actively use MacOS.

@no-response
Copy link

no-response bot commented Jun 25, 2020

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

@no-response no-response bot closed this as completed Jun 25, 2020
@Ghostkeeper
Copy link
Collaborator

😠

@Ghostkeeper Ghostkeeper reopened this Jun 25, 2020
@Ghostkeeper Ghostkeeper removed the Status: Needs Info Needs more information before action can be taken. label Jun 25, 2020
@Vandrasc
Copy link
Contributor

I cannot reproduce either on os x, the models can be successfully selected when clicking on the models. I propose to close this ticket.

@Ghostkeeper
Copy link
Collaborator

@rreilink told me last week via Teams that he's still experiencing this bug.

@rreilink
Copy link
Author

rreilink commented Jul 6, 2020

The bug only occurs occasionally. I have updated the description to incorporate this.

@rreilink rreilink changed the title [4.1.0] Objects cannot be selected after slicing and then switching back to 'Prepare' [4.1.0] Sometimes, objects cannot be selected after slicing and then switching back to 'Prepare' Jul 6, 2020
@Ghostkeeper
Copy link
Collaborator

Those are the hardest type of bugs to find!

@GregValiant GregValiant added Status: Needs Info Needs more information before action can be taken. Status: Stale ⌛ This issue is over a year old. It might be obsolete or just needs a fresh set of eyes labels Nov 21, 2024
@GregValiant
Copy link
Collaborator

I'm cleaning house.
Is this still a problem with current Cura versions (5.8.0 and up)? Can I close this?

Copy link
Contributor

github-actions bot commented Dec 7, 2024

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

@github-actions github-actions bot closed this as completed Dec 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Needs Info Needs more information before action can be taken. Status: Stale ⌛ This issue is over a year old. It might be obsolete or just needs a fresh set of eyes Type: Bug The code does not produce the intended behavior.
Projects
None yet
Development

No branches or pull requests

6 participants