Forum

Hi,
after I update Prof-UI from v2.64 to v2.82,
the speed of UI refresh and initializing become very slow.
How to improve speed ?
thanks.

Hello~ Support Sir~

Any body home ?

Could someone answer me ?! Please !!

I have waiting for several days !

Hello~

Any body home ?

Could someone answer me ?!

Hi,

Could you give me a response ? I have waiting for several days !!!

I am looking forward to your reply. Please reply ! Thanks.

Yes, we received it and answered you by e-mail.

We got same problem with 2.82 (oh. my post was gone or this post may be duplicated..sorry...)
We just upgrade from 2.62 and nothing was changed in our code.
But the UI refresh/initialization speed was significantly slow down.
Only we’re doing was calling DX rendering at xxxApp::OnIdle() but this was ok with 2.62.
Please let us know how to fix it and we should downgrade to 2.62 until then.

If you type some text in some editor, press some keys to change the selection in some control, move the mouse pointer over some windows, click, resize or move something in your application, then the appropriate messages are posted to the thread’s message queue. The CWinApp::Run() virtual method extracts the messages from the queue and delivers them to appropriate window procedures. If there are no messages in the queue, then the CWinApp::OnIdle() virtual method is invoked. The idle processing should not do anything complex and heavy. If you set some timer to some window, then it posts the WM_TIMER messages to the threads message queue. So, even if the user does not perform any input, the CWinApp::OnIdle() virtual method is invoked periodically. Mostly we do not use timers. We use timers only during some algorithms for tracking mouse hover, drag-n-dropping algorithms (such as control bar redocking) and in-place activated editor controls (in grids and some other controls). It’s good idea to implement Direct X or Open GL code in a stand-alone thread. The GLViews sample draws scenes into a memory buffer. The picture frames are painted in a standalone thread by requests from the main UI thread and then picture data is transferred to the main thread. In any case, you should trace how often the CYourApp::OnIdle() virtual method is invoked in different states of your application and find out when the un-needed messages are posted into the thread’s message queue.

Do you use any time consuming code in the command updating methods and/or idle time processing methods?

No, I just create some ResizableDialog with many control items.
I have mail my project to you, please give my some advices for speed up, thanks.

Dear Support sir,

Have you got my project code on your support mail address?