Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

About performance optimization/better build scenarios #74

Open
childeyouyu opened this issue Jan 30, 2024 · 3 comments
Open

About performance optimization/better build scenarios #74

childeyouyu opened this issue Jan 30, 2024 · 3 comments

Comments

@childeyouyu
Copy link

A month ago, I reported that constantly generating multiple tables would cause the interface to flicker, and there was no good solution at that time, and finally decided to generate a new single-row table after reading the data every time and put it at the bottom, the code is as follows:

    def update_values(self, values, used_devices):
        # 将读取来的数据填充到相应的表格里
        # 在相应的 tab 下生成表格
        for used_device in used_devices:
            # value 的判断
            value = []
            for i in values[int(used_device[1][-1]) - 1]:
                value.append(i)
            # value = values[used_devices.index(used_device)]
            table = CTkTable(master=self.table_list.get(used_device[0]), corner_radius=0, values=[value])
            table.pack(fill="both", expand=True)

However, my solution is not good, it will cause a lot of waste in performance, even on my 16G computer, let alone send it to customers.
Is there any good change or other solution to my code/requirements?

@iLollek
Copy link

iLollek commented Mar 21, 2024

bump. Please improve the rendering performance!

@Akascape
Copy link
Owner

@iLollek Will work on this, probably have to make a separate widget.

@iLollek
Copy link

iLollek commented Mar 21, 2024

@Akascape thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants