CXTPStatusBar::SetPaneText missing bUpdate arg

Author

Message

Topic Search

Topic Options

mrmathis

Senior Member

Joined: 17 May 2007
Location: United States
Status: Offline
Points: 105

Post Options

Post Reply

Quote mrmathis

Report Post

Thanks(0)

Quote

Topic: CXTPStatusBar::SetPaneText missing bUpdate arg
Posted: 12 August 2008 at 11:50am

I'm moving from Codejock 11 to 12 and found that CXTPStatusBar has removed the bUpdate argument from SetPaneText. It is still mentioned in the comment above the function declaration, and the help file SymbolReference.chm doesn't show it in the prototype but does still document it. I don't see any documentation for the change in the release_notes.htm or migrating_guide.htm, or here on the forums.

What happened to the arg? Do I need to handle the invalidate myself? Does it always update now? I see that the code has changed a good bit, but I'm not sure how I should react (if at all).

--Mike

Oleg

Admin Group

Joined: 21 May 2003
Location: United States
Status: Offline
Points: 11234

Post Options

Post Reply

Quote Oleg

Report Post

Thanks(0)

Quote

Posted: 13 August 2008 at 1:24am

Hi,

Please just remove this last parameter - statusbar now handle it automatically.

Oleg, Support Team
CODEJOCK SOFTWARE SOLUTIONS

rdhd

Senior Member

Joined: 13 August 2007
Location: United States
Status: Offline
Points: 899

Post Options

Post Reply

Quote rdhd

Report Post

Thanks(0)

Quote

Posted: 08 April 2009 at 11:32am

Now that the flag is missing, users are not seeing all of our message strings. I don't know if that is due to the flag or some other issue in the new version. Now we have to call SetPaneText and then call SendMessage( WM_PAINT ) to force the pane to display the text. The problem is that as we are sometimes doing extensive processing and while doing so we send a number of messages we want the user to see immediately. It looks like WM_PAINT messages appear to be going onto the message queue and by the time our processing is done and the system starts processing messages on the queue, we have set the text a number of times and the user only sees the last text we set when OnPaint is finally called.

So it appears that not only do we have to re-edit existing code (you could have just left the parameter there if you believed the semantics of the function did not change and there would have been no compile issues), but once again when we moved to a newer version of CJ, we have found yet another issue with code that used to work and have had to come up with another work-around to restore the previous behavior.

Smucker

Senior Member

Joined: 02 February 2008
Status: Offline
Points: 156

Post Options

Post Reply

Quote Smucker

Report Post

Thanks(0)

Quote

Posted: 08 April 2009 at 5:23pm

Nothing to do with Codejock per se; any long-running code should either be relegated to another thread or regularly handle messages during its execution. Otherwise the application becomes unresponsive.

I would also recommend calling UpdateWindow() rather than sending WM_PAINT directly; UpdateWindow() will generate the correct parameters for the paint message.

Even then, on Vista Aero you may not see every message because of the DWM.

Product: Xtreme Toolkit Pro version 13.2 (Unicode, static build)

Platform: Windows 200x/XP/Vista/Win7 (32/64 bit)

Language: Visual C++ 9.0 (Studio 2008)

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
mrmathis Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 17 May 2007 Location: United States Status: Offline Points: 105	Post Options Post Reply Quote mrmathis Report Post Thanks(0) Quote Reply Topic: CXTPStatusBar::SetPaneText missing bUpdate arg Posted: 12 August 2008 at 11:50am
	I'm moving from Codejock 11 to 12 and found that CXTPStatusBar has removed the bUpdate argument from SetPaneText. It is still mentioned in the comment above the function declaration, and the help file SymbolReference.chm doesn't show it in the prototype but does still document it. I don't see any documentation for the change in the release_notes.htm or migrating_guide.htm, or here on the forums. What happened to the arg? Do I need to handle the invalidate myself? Does it always update now? I see that the code has changed a good bit, but I'm not sure how I should react (if at all). --Mike
	--Mike

Oleg Members Profile Send Private Message Find Members Posts Add to Buddy List Admin Group Joined: 21 May 2003 Location: United States Status: Offline Points: 11234	Post Options Post Reply Quote Oleg Report Post Thanks(0) Quote Reply Posted: 13 August 2008 at 1:24am
	Hi, Please just remove this last parameter - statusbar now handle it automatically.
	Oleg, Support Team CODEJOCK SOFTWARE SOLUTIONS

rdhd Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 13 August 2007 Location: United States Status: Offline Points: 899	Post Options Post Reply Quote rdhd Report Post Thanks(0) Quote Reply Posted: 08 April 2009 at 11:32am
	Now that the flag is missing, users are not seeing all of our message strings. I don't know if that is due to the flag or some other issue in the new version. Now we have to call SetPaneText and then call SendMessage( WM_PAINT ) to force the pane to display the text. The problem is that as we are sometimes doing extensive processing and while doing so we send a number of messages we want the user to see immediately. It looks like WM_PAINT messages appear to be going onto the message queue and by the time our processing is done and the system starts processing messages on the queue, we have set the text a number of times and the user only sees the last text we set when OnPaint is finally called. So it appears that not only do we have to re-edit existing code (you could have just left the parameter there if you believed the semantics of the function did not change and there would have been no compile issues), but once again when we moved to a newer version of CJ, we have found yet another issue with code that used to work and have had to come up with another work-around to restore the previous behavior.

Smucker Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 02 February 2008 Status: Offline Points: 156	Post Options Post Reply Quote Smucker Report Post Thanks(0) Quote Reply Posted: 08 April 2009 at 5:23pm
	Nothing to do with Codejock per se; any long-running code should either be relegated to another thread or regularly handle messages during its execution. Otherwise the application becomes unresponsive. I would also recommend calling UpdateWindow() rather than sending WM_PAINT directly; UpdateWindow() will generate the correct parameters for the paint message. Even then, on Vista Aero you may not see every message because of the DWM.
	Product: Xtreme Toolkit Pro version 13.2 (Unicode, static build) Platform: Windows 200x/XP/Vista/Win7 (32/64 bit) Language: Visual C++ 9.0 (Studio 2008)