The current plugin version does not work with a new Cura release

[fieldOfView]

When a new release of Cura is available, the Sidebar GUI plugin always needs to be updated.

In order for the Sidebar GUI plugin to work, it does quite a bit of "nasty" patching of the original interface. These patches may break the interface when the original interface is changed. So, as a security measure, the plugin checks to see if it has been "approved" for the version of Cura you are using it with.

I normally work hard to have an updated version of the plugin ready during the beta period, so when a new stable release of Cura is available, the plugin update is available in the Marketplace. Because I may not always have time immediately when a Cura beta is released, and because updates to plugins need to be checked and approved by Ultimaker developers, there is always a bit of a delay.

Edit:
Since the beta period of Cura 5, prereleases (and stable versions) can be found here:
https://github.com/fieldOfView/Cura-SidebarGUIPlugin/releases

To install a release from that page, download the .curapackage appropriate for the version of Cura you use, and drop the .curapackage file onto the buildplate in Cura as if you were opening a 3d model. Restart Cura when instructed.

[Thisismydigitalself]

SidebarGUIPlugin_v4.3.0-DEV_Cura5.0 works for me. thank you Aldo.

[fieldOfView]

It is that time of the month again with a new beta of Cura out. I have created a new prerelease that is compatible with Cura 5.1. I don't have a lot of time to test it myself right now, so it would be nice if some of you could install and test this prerelease:

https://github.com/fieldOfView/Cura-SidebarGUIPlugin/releases/tag/v4.4.0-DEV

Download the SidebarGUIPlugin_v4.4.0-DEV_Cura5.0.curapackage, and drop the resulting file onto the buildplate in Cura as it you were opening a 3d model.

(note to self: fix packager so it is clearer that the release is for 5.0 and up)

[Thisismydigitalself]

Just installed 4.4.0 on 5.1 and we're back in business.
thank you Aldo.
your plugs are used by hundreds of thousands of users and this alone tells me that Cura team should take that into account each time they release a new version.

Keep up the good work.
Cheers.

[fieldOfView]

Thanks for the kind words, @Thisismydigitalself

[pnt103]

I just installed 4.4.0-DEV (Cura 5.1.0), and that fixed things for me too. Thank you!

[yet-another-average-joe]

Thanks for the update.
I was desesperating !

[erickwill]

Looking forward for a new update in order to fix it to work along with the new cura version 5.6.0

[yet-another-average-joe]

Thanks. Wasn't notified for 5.6.
5.5 was such a disaster that I immediately reverted to 5.4.0.
5.5, the "unable to slice" slicer ; but slicing when changing a bit any parameter. While Cura is the best slicer, by far. Slic3r descendants are toys, Cura being the only real tool. And Sidebar the add on that makes it usable ; should be mainstream.

Sorry for the rant.

Will no install 5.6 until Sidebar supports it. I stay tuned.
(of course, being a end user, I just rant, I don't paticipate ;) )

[fieldOfView]

If you actually read the opening post, it has a link to this page:
https://github.com/fieldOfView/Cura-SidebarGUIPlugin/releases

That page has a prerelease of the plugin that is compatible with Cura 5.6.

[yet-another-average-joe]

Thanks !

[GregValiant]

Hello Aldo.
I adjusted the version number in SidebarGUI (and TabbedSettings) so they would load in 5.10beta. (That is my normal routine and hasn't been a problem.)

This could just be me being impatient, but here is what I've noticed.

In 5.10beta-1:

• TabbedSettings is throwing QML errors and isn't loading.

In regards to SideBarGUI...

• The "printer box" is not populated with the installed printers. I have to use "Settings/Printers/Manage printers" to change machines. The selected printer correctly appears in the text area of the dropdown (but the dropdown list is empty).

• The "profile box" seems to have issues. The original box remains but the selected profile does not appear in the text area of the dropdown (but the list is populated).

• The original "profile box" remains and works.

[fieldOfView]

That must be why I don't have a beta yet... More work than just upping the version number is needed this time, and this is exactly why I have implemented the version check in the first place.