Replies: 2 comments 1 reply
-
Screenshot/截图 |
Beta Was this translation helpful? Give feedback.
0 replies
-
In different Python versions Miraculously, I tested the script using the installed version of python, and it became very fast and usable |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Machine Translation
I've been waiting for DPG to add treeview control for a long time. I'm glad DPG included treeview in the plan a few days ago. Like issue#1395, I use the treeview control as often as I do. Therefore, send out the treeview prototype code, which can be used for reference and temporary testing by those in need.
This is the second draft. It combines the tree with the display control. It's a little faster. Dpg.move_Item() is used, because the row hiding function cannot be found. Row items moves between the table and stage, and then cooperates with dpg.reorder_Items() rearranges the display lines. One of the reasons for the slowness of draft 2 is that every time move_Item() is called will call rendering, I guess. I want to find the function of rendering at the end ,when a large number of nodes are moved, but I can't find it. The second reason why draft 2 is slow is that it takes a long time to generate a list of tree nodes arranged in sequence. The first draft is a tree data structure, which is separated from the display control. The control is only used for display. The first draft is slower.
I'm waiting for the release of DPG's treeview widget. I hope it has the clipping function of dpg.table. I used to use Tkinter's treeview control to create a large number of tree nodes. Finally, it was so slow that it was difficult to drag the interface. I speculate that the displayed interface has a range, but it actually renders the interface of the complete tree. In fact, I can't verify this speculation.
代码
Beta Was this translation helpful? Give feedback.
All reactions