The problem is that it might take a while before we can see Modelio using Java 11 and your patch could be applied quickly, effectively solving the bug from a functional point of view, before the migration occurs later on. Having a version of Modelio which works with GTK 3 would be more valuable than a version which doesn't, even if I understand some people would argue that it's a hack and things should be done the right way. Since it will probably take some time before Modelio is migrated to Java 11, would it be possible to apply this patch one way or another on the Modelio source code (more precisely on the JDK that it embeds, if I understand the bug report correctly) temporarily until Modelio is migrated to Java 11? In the bug report that you posted ( ), you said that you wrote a patch to fix it. So updating to Java 11 would solve the high CPU usage when using GTK 3. Thank you so much for all these details, it looks like you spotted the exact origin of the bug. I tried turning off font anti-aliasing by putting these options in modelio.ini: I tried switching to different GTK3 themes like Arc, Breeze, Adwaita:dark, it didn't change anything. With wide modeling coverage of UML, BPMN, requirements and goals, the Modelio metamodel is complete, open and well documented. I tried changing the display backend using GDK_BACKEND=wayland in Gnome but Modelio wouldn't run, it wants x11. Modelio has always been a pioneer in the implementation of the OMGs MDA (Model Driven Architecture) technology. GTK3 should obviously be used over GTK2 since it supports HiDPI scaling and is supposed to be future proof with the support of Wayland, so I think we should really address this issue.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |