![]() ![]() Target platform is currently GNU/Linux desktop. Should I try to replace GTK-3.0 with something else, and if so, what? I think it is a good idea to know how good the library is at handling user movable widgets, so porting the UI part would be worth the effort. Then, when you consume your PCL library in a regular. If this library is referenced from your PCL library, you can use Serializable in your code. ![]() The down-side to this is that the PCL must reduce itself to the lowest common set of classes which are compatible across ALL the specified platforms. The widget canvas is much like a GtkLayout, with support for multiple "layers". I have created a PCL support library called CSShim that contains a 'mock' Serializable attribute. With the introduction of the Portable Class Library, developers can release a single library which is compatible across multiple platforms. The connections are drawn on top of the other widgets. The purpose of the widget canvas is to implement a "Node editor", similar to what you find in Blender. The project is an addition of 11,000 sf of movable library file storage, doubling the size of the original precast building. The widgets mainly contains GtkLabels and GtkSliders.įor reference, here is a link to the project: Operator() basically calls gtk_container_propagate_draw on each child widget. Ui/line_segment_renderer.cpp:draw_callback:56 33100 ns After benchmarking, I have found that gtk_container_propagate_draw is a huge bottleneck: ui/widget_canvas_internal.cpp:operator():73 29046505 ns As soon as the number of widget increases, I get frametimes whell above 20 ms. The user is able to move native GtkWidgets by dragging them around, pretty much like MDI. After hard work, I have managed to write a working "widget canvas" for GTK-3.0. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |