Not jumping to device tab after sending job

[SwagDad99]

Describe the bug
The print dialog shows a counter, counting down until it jumps to the device tab. It hits '0', and just goes back to the preview tab, instead of jumping to the device tab like it used to.

3mf File for This Bug
If it is related to slicing, please append the 3mf file. It could be extremely helpful to solve the issue.

To Reproduce
Send a job to the printer and wait

Expected behavior
It should jump to the device tab

Screenshots
If applicable, add screenshots to help explain your problem.

Printer model
X1C

Desktop (please complete the following information):

• OS: Windows
• Version 11 Home

[Merlwynd]

Yes, same thing happens with me. Not a huge concern as I just open device tab…but it should go there automatically after countdown finishes.

[SwagDad99]

I agree, it isn’t a big concern, just a minor bug that should be brought up as long as other fixes are going in... There are actually times I am fine with it not jumping to the device tab. Like when I am starting prints on multiple printers... Don From: Merlwynd Sent: Wednesday, March 22, 2023 11:40 PM To: SoftFever/OrcaSlicer Cc: SwagDad99 ; Author Subject: Re: [SoftFever/OrcaSlicer] Not jumping to device tab after sending job (Issue #567) Yes, same thing happens with me. Not a huge concern as I just open device tab…but it should go there automatically after countdown finishes. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

[Merlwynd]

I only have one printer, but I can see your point on multiple printers. If the majority of opinion is not to automatically jump to device page, I guess I'm ok with that as easy enough to click on device tab, but then they should remove the automatic message and the countdown clock...just want things to be consistent either way...

[SwagDad99]

Exactly. I agree with your statement. Don From: Merlwynd Sent: Thursday, March 23, 2023 12:06 PM To: SoftFever/OrcaSlicer Cc: SwagDad99 ; Author Subject: Re: [SoftFever/OrcaSlicer] Not jumping to device tab after sending job (Issue #567) I only have one printer, but I can see your point on multiple printers. If the majority of opinion is not to automatically jump to device page, I guess I'm ok with that as easy enough to click on device tab, but then they should remove the automatic message and the countdown clock...just want things to be consistent either way... — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

[eboston]

I only have one printer, but I can see your point on multiple printers. If the majority of opinion is not to automatically jump to device page, I guess I'm ok with that as easy enough to click on device tab, but then they should remove the automatic message and the countdown clock...just want things to be consistent either way...

Before the latest release, it would switch to the device tab so it seems like something broke with the last release. I can also see where not switching could be useful. Instead of hardcoding an action, maybe an option can be added so the user can select whether to switch or not.

[davemartin88]

Just downloaded and used OrcaSlicer 1.6, still not jumping to device tab after sending. X1C

[Marcel40625]

bug still exists with 1.6.0 for me!

[julie777]

Strangely enough, although it doesn't jump to the device page, it does connect to the device and update status, and start the camera play. Both of these usually take noticeable time to start after sending a print so it is doing part of the switch task.

[maziggy]

Same here with latest version.

[Marcel40625]

Issue stills persists in 1.6.2-beta

[julie777]

Please make this a priority.
In addition to jumping to the device page, I think it would be a good idea to get rid of the 3 second countdown. Why not jump as soon as the job is sent.

There are two issues related to this.

1. because it doesn't jump immediately, I don't feel like waiting for the countdown and switch to another window
2. Because I am not looking at the device page when the printer is parsing the gcode/3mf file, I don't notice that the parse failed and then later when I check the job status I find that it never actually started.

[Marcel40625]

Issue stills persists in 1.6.2 !!!!

[github-actions]

GitHub bot: this issue is stale because it has been open for 90 days with no activity.

[Merlwynd]

GitHub bot: this issue is stale because it has been open for 90 days with no activity.

GitHub bot: this issue is stale because it has been open for 90 days with no activity.

This should be closed as no longer an issue in latest versions….

[github-actions]

Orca bot: this issue is stale because it has been open for 90 days with no activity.

[github-actions]

Orca bot: This issue was closed because it has been inactive for 7 days since being marked as stale.