-
Notifications
You must be signed in to change notification settings - Fork 58
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
No selection of spool #73
Comments
Could you please also provide the content of the Javascript console from your browser? |
Hello,
Do you know how to activate on Safari browser on Mac?
Best regards,
Christian
Am 14.01.2018 um 12:51 schrieb Sven Lohrmann <notifications@github.com<mailto:notifications@github.com>>:
Could you please also provide the content of the Javascript console from your browser?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#73 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AVSo8ynNoI0l2rl6vk4W0iJfC4Ma-W2Dks5tKepGgaJpZM4Rdj1A>.
|
No sorry I don't know that. I also have to say that I'm not supporting the Safari browser because I don't own any apple device and therefore I cannot test with that browser. Maybe you could try it with a chromium based browser or firefox. |
OK – I will try it with Google Chrome on Mac!
Best regards,
Christian
Von: Sven Lohrmann <notifications@github.com>
Antworten an: malnvenshorn/OctoPrint-FilamentManager <reply@reply.github.com>
Datum: Sonntag, 14. Januar 2018 um 13:19
An: malnvenshorn/OctoPrint-FilamentManager <OctoPrint-FilamentManager@noreply.github.com>
Cc: Christian Scharringer <christian@scharringer.de>, Author <author@noreply.github.com>
Betreff: Re: [malnvenshorn/OctoPrint-FilamentManager] No selection of spool (#73)
No sorry I don't know that. I also have to say that I'm not supporting the Safari browser because I don't own any apple device and therefore I cannot test with that browser. Maybe you could try it with a chromium based browser or firefox.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#73 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AVSo83H2sq6ThsChplAuqq0tk5WNjTynks5tKfDcgaJpZM4Rdj1A>.
|
Yes that's what I meant. But I cannot see any error. Because the dialog shows only selections for tools which are actually used by the print job I would explain this behavior with the fact that the analyzing process of the selected file is not finished at the time the dialog opens. This would correspond to the fact that the selection appears after some retries. It would be great if you could verify that in your case. |
I had this right now too, but in Firefox. |
Here is the provided Link in the Message above |
What I found out. When under "Status" the correct weight and tool is not red or calculated, your pop-up is empty. I had to refresh my browser site and/or load a different file and load the specific file again until the "Status" is correct. |
Thanks. I think this confirms my previous speculation. I'm going to revise the dialog so that the user isn't confronted with an empty dialog and don't know why this happened. |
Yeah you're right. But please leave this popup. We should solve the problem why the status isn't updated. |
@TylonHH the only cases where this should happens are:
If this issue appears after the used filament and print time has been updated in the sidebar then we might have a bug somewhere. |
@malnvenshorn you're right. That's what I ment, that someone is responsible. |
It would also be nice if after that window shows up with the list of spools to select that the currently selected spool on the main screen would be preselected. |
@szafran81 see #71 |
Added some information to the confirmation dialog if no selection is available to explain the cause of this. If I get some information that show that there is a bug in the filament manager after all I'll reopen this ticket. |
I think it is bug: https://discourse.octoprint.org/t/selecting-problem-in-filamentmanager/ |
It's not a bug of the filament manager plugin. Because this plugin don't analyze the gcode. |
Unfortunately the video from the linked post doesn't show whether the file was fully analysed before the dialog was opened or not. Therefore I'm assuming the file was not analysed yet. In this case the behavior is as intended. |
I have the same issue. |
It seems out of my list of filaments, only one is useable.(rPLA RED) |
I think I've found the issue. You have to make sure that the filament you want to use is selected in the tool box, and matches the one that you then select in the confirmation dialog. For me it's more an issue of not guiding the user well enough, but not a bug. So first, select the filament you want to use in the 'tool window' of Filament manager, then hit print and confirm the SAME filament in the confirmation pop-up. IMHO, it would be better to allow the user to switch filament in that confirmation window, but make clear that you SWITCH to a different filament. Maybe add a button "change filament" ? |
I was confused as well. I even anticipated that this is happening..., but couldn't find option in the settings to change filament.
|
When pressing on "Print" the selection screen for the spool is not shown and the Button "Start Print" is inactive.
When I retry 4 to 5 time the selection for the spool is shown
What were you doing?
Press on button "Print" (in tho top) or on the Button "Print" above a single file.
What did you expect to happen?
The dropdown for the spool should be shown
What happened instead?
The dropdown for the Spool is missing
Link to octoprint.log
octoprint.log
Link to gcode file
[If you encounter issues with the odometer feature provide a small gcode file which produces the problem.]
Link to contents of Javascript console in the browser
[If you're reporting UI issues always include the output of the javascript console of your browser. Always include if unsure.]
Further information
I have read the FAQ and provided all required information.
The text was updated successfully, but these errors were encountered: