-
Notifications
You must be signed in to change notification settings - Fork 216
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
ScreenViewport.waitForSceneCompletion does not resolve under certain conditions #7618
Comments
Hi @thanhbinh-d, can you please provide steps to reproduce? |
The bug description was updated. |
@raplemie are you able to provide iTwin+iModel Id and grant read access to me and @markschlosseratbentley? |
@markschlosseratbentley @pmconne added, this iModel is in QA: (Mentioning changeset as later changeset modify the location of the additional graphics and do not exhibit the same issue) |
Hi @raplemie and @thanhbinh-d I am trying to reproduce this locally where it is easier to debug. I can make this problem happen in the Civil frontstage of your linked web app. However, I am having trouble doing it locally. Is this particular sheet view "A001 cord22 - 606+50xxx" available in a standalone .bim file of this iModel (which I downloaded)? Locally, I see "cord22 - 606+50.00 [Sheet] Views - View 1", but it does not reproduce the issue. It visually looks similar. I am using the |
Hi @markschlosseratbentley The sheet “A001 cord22 - 606+50.00 [Sheet]” is associated with three drawing view definitions, not a sheet view definition. I will send you some related images in person soon. Regarding the other question, perhaps @raplemie can provide more insights. |
Describe the bug
When a sheet contains a Drawing attachment with an incorrect X offset, the function
waitForSceneCompletion
does not resolve. This causes the application to hang indefinitely, preventing further actions.Steps to Reproduce:
Expected behavior
The function
waitForSceneCompletion
should resolve even when there are incorrect Drawing attachments, ensuring that the viewport scene completes rendering regardless of attachment issues.Suggestion for Improvement:
To make the API more robust and user-friendly, consider adding an optional timeout parameter to the waitForSceneCompletion function. This would allow developers to specify a maximum wait time, preventing indefinite hangs in edge cases like this.
For example:
await viewport.waitForSceneCompletion({ timeout: 100 }); // Timeout in milliseconds
Screenshots
The text was updated successfully, but these errors were encountered: