Fedora 24 will be a sad release for 3D printing :(
Does anyone have time to look at this? Unfortunately, I'm busy with my diploma thesis.
-------- Forwarded Message -------- Subject: [Bug 1323598] New: Cura has lots of repaint issues in the GUI Date: Mon, 04 Apr 2016 08:07:08 +0000 From: bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1323598
Bug ID: 1323598 Summary: Cura has lots of repaint issues in the GUI Product: Fedora Version: 24 Component: cura Assignee: mhroncok@redhat.com Reporter: tigert@redhat.com QA Contact: extras-qa@fedoraproject.org CC: mhroncok@redhat.com
Description of problem: Cura has a lot of repaint issues on Fedora 24, lots of gtk errors on console and the widget sizes get messed up.
I was wondering if the new version of GNOME shell would cause something, but the same happens also with WindowMaker (ha, blast from the past!).
Version-Release number of selected component (if applicable): cura-15.04.4-3.fc24.noarch
How reproducible: always
Steps to Reproduce: 1. open cura 2. see console and how the viewport has issues when you resize window
Additional info:
Console shows a lot of these:
(cura:6018): Gtk-WARNING **: Allocating size to wxPizza 0x55f955e03710 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
(cura:6018): Gtk-WARNING **: Allocating size to wxPizza 0x55f955e03870 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
(cura:6018): Gtk-WARNING **: Allocating size to wxPizza 0x55f956f45440 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
(cura:6018): Gtk-WARNING **: Allocating size to GtkNotebook 0x55f955718510 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
(cura:6018): Gtk-WARNING **: Allocating size to wxPizza 0x55f956f45860 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
(cura:6018): Gtk-WARNING **: Allocating size to GtkLabel 0x55f956a1cae0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
(cura:6018): Gtk-WARNING **: Allocating size to GtkSeparator 0x55f956a870f0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
(cura:6018): Gtk-WARNING **: Allocating size to wxPizza 0x55f956f45b20 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
Oh no!! Some people use Cura very offen, even daily. I used to depend on it when I worked in DFROBOT.
I think it may not the only distribution-related issue, if GNOME 3.20 makes all things mass up, it should happen in Debian Testing and openSUSE Tumbleweed very soon. Thus, good news , it may attract more attentions helping us to solve the problem.
于 2016年4月4日 GMT+08:00下午7:59:09, "Miro Hrončok" mhroncok@redhat.com 写到:
Fedora 24 will be a sad release for 3D printing :(
Does anyone have time to look at this? Unfortunately, I'm busy with my diploma thesis.
-------- Forwarded Message -------- Subject: [Bug 1323598] New: Cura has lots of repaint issues in the GUI Date: Mon, 04 Apr 2016 08:07:08 +0000 From: bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1323598
Bug ID: 1323598 Summary: Cura has lots of repaint issues in the GUI Product: Fedora Version: 24 Component: cura Assignee: mhroncok@redhat.com Reporter: tigert@redhat.com QA Contact: extras-qa@fedoraproject.org CC: mhroncok@redhat.com
Description of problem: Cura has a lot of repaint issues on Fedora 24, lots of gtk errors on console and the widget sizes get messed up.
I was wondering if the new version of GNOME shell would cause something, but the same happens also with WindowMaker (ha, blast from the past!).
Version-Release number of selected component (if applicable): cura-15.04.4-3.fc24.noarch
How reproducible: always
Steps to Reproduce:
- open cura
- see console and how the viewport has issues when you resize window
Additional info:
Console shows a lot of these:
(cura:6018): Gtk-WARNING **: Allocating size to wxPizza 0x55f955e03710 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
(cura:6018): Gtk-WARNING **: Allocating size to wxPizza 0x55f955e03870 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
(cura:6018): Gtk-WARNING **: Allocating size to wxPizza 0x55f956f45440 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
(cura:6018): Gtk-WARNING **: Allocating size to GtkNotebook 0x55f955718510 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
(cura:6018): Gtk-WARNING **: Allocating size to wxPizza 0x55f956f45860 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
(cura:6018): Gtk-WARNING **: Allocating size to GtkLabel 0x55f956a1cae0
without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
(cura:6018): Gtk-WARNING **: Allocating size to GtkSeparator 0x55f956a870f0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
(cura:6018): Gtk-WARNING **: Allocating size to wxPizza 0x55f956f45b20 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
3dprinting mailing list 3dprinting@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/3dprinting@lists.fedoraproject.or...
I'll take a look at this later today. I'm not going to make any promises, of course. I should be able to tell why the repaint issues happen, if nothing else.
On 04/04/2016 08:51 AM, John M. Harris, Jr. wrote:
I'll take a look at this later today. I'm not going to make any promises, of course. I should be able to tell why the repaint issues happen, if nothing else.
I'm pretty sure this is because of changes in gtk3 that require changes in wx. I was working on this for a while and helped make some changes in upstream wx git.
~tom
== Red Hat
On Mon, 2016-04-04 at 09:39 -0400, Tom Callaway wrote:
On 04/04/2016 08:51 AM, John M. Harris, Jr. wrote:
I'll take a look at this later today. I'm not going to make any promises, of course. I should be able to tell why the repaint issues happen, if nothing else.
I'm pretty sure this is because of changes in gtk3 that require changes in wx. I was working on this for a while and helped make some changes in upstream wx git.
Maybe we should involve Benjamin Otte ? Apparently he's done work in that area of GTK specifically.
Simo.
On Mon, 2016-04-04 at 09:39 -0400, Tom Callaway wrote:
On 04/04/2016 08:51 AM, John M. Harris, Jr. wrote:
I'll take a look at this later today. I'm not going to make any promises, of course. I should be able to tell why the repaint issues happen, if nothing else.
I'm pretty sure this is because of changes in gtk3 that require changes in wx. I was working on this for a while and helped make some changes in upstream wx git.
~tom
== Red Hat
Ah, alright. That takes about 2 hours of debugging off of my list of things to do. Thanks
Hi,
I'm pretty sure this is because of changes in gtk3 that require changes in wx. I was working on this for a while and helped make some changes in upstream wx git.
Oh, okay great. I didn't notice this mail before. I guess the upstream change to cherry-pick is this one:
https://github.com/wxWidgets/wxWidgets/commit/9fea81c069f9d803d79c4ce82f87a0...
--Ray
On 04/04/2016 02:15 PM, Ray Strode wrote:
Hi,
I'm pretty sure this is because of changes in gtk3 that require changes in wx. I was working on this for a while and helped make some changes in upstream wx git.
Oh, okay great. I didn't notice this mail before. I guess the upstream change to cherry-pick is this one:
https://github.com/wxWidgets/wxWidgets/commit/9fea81c069f9d803d79c4ce82f87a0...
Yep. That fix resolves the issue for me. I'm building updated packages now (wxGTK3-3.0.2-19.fc25, wxGTK3-3.0.2-19.fc24).
~tom
== Red Hat
Hi,
Does anyone have time to look at this? Unfortunately, I'm busy with my diploma thesis.
Someone pinged me on IRC about this and asked if I had any insight. I've done a scratch build that seems to work around the problem here:
http://koji.fedoraproject.org/koji/taskinfo?taskID=13556591
But the patch isn't really right, just a stopgap. The widget container code should be changed to stop hardcoding a minimum and natural size of zero, and instead take the size of the container's children in account when producing its own preferred size. The best person to talk to about this is Benjamin Otte (Company on #gtk+ on gimpnet).
3dprinting@lists.fedoraproject.org