Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » U++ Library support » U++ Widgets - General questions or Mixed problems » Having my HWND and eating it, too...
Re: Having my HWND and eating it, too... [message #12099 is a reply to message #12098] Wed, 10 October 2007 22:31 Go to previous messageGo to previous message
Oblivion is currently offline  Oblivion
Messages: 1135
Registered: August 2007
Senior Contributor
Ah, I see. I'm converting my MFC-based multiprotocol (so a client-server system is used) messenger to UPP and encountered similar problems.

Well, AFAIK it is not possible that way. If I understand it right, you derive your child windows from TopWindow, but you do not Open() them. Unless they are opened, they cannot be TopWindows; they stay as ctrl (which -- conceptually -- has no HWND). On the other hand, if they are Opened() they cannot be child ctrls anymore, at most they can be child top or popup windows. If your client programs are in U++ too, you could pass ctrl* instead. But if they are not, and you are trying to "draw" something, you could pass a "Rect" and an ID to the ctrl (this means that you have to modify your apps IPC message framework.

Namely, as far as I know there is no HWND of ctrls "in the main window." (AFAIK, not explicitly). Sad



[Updated on: Wed, 10 October 2007 22:43]

Report message to a moderator

 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message icon3.gif
Read Message
Previous Topic: Toolbar clears after ESC key [solved, it`s the bug in user code]
Next Topic: label text not wrapped
Goto Forum:
  


Current Time: Fri Nov 01 01:03:22 CET 2024

Total time taken to generate the page: 0.00894 seconds