1. Get the Client rectangle of the Dialog Box. ( Use: GetClientRect(LPRECT))
2. Calculate the new size of controls.
4. Validate whether the dialog controls are valid window ( Use; IsWindow( HWND ))
5. Move dialog controls to the new position i they are valid windows.
Layout manager in Java ( Like you said ) will automatically resize the controls in the window.
Since we have a very simple method to resize the controls in MFC, designing a layout manager is overhead to the developer.
In Java it's depends upon the personel interest since there are both the features are readly available.
its really depends upon the persnel interest. I respect you interest. I believe Layout can generalize the functionality, but my code do the same in simple and a few lines.
While I was working with layout managers in Java, i feel i have only a less freedom to move the control over the window. And I satrted to put NULL in the Java Window layout and moved my controls independently.
This code is expected to work only when the Dialog is forcely resize by using Minimize, Maximize, Drag Size etc. To resize the control in Initial state you have to put some similiar code in the OnInitDialog of the dialog class like
In OnInitDialog you do not have to check the Window handle because OnInitDialog is called after the creation of the Dialog Box and it's control. But you should check the Validity of m_edit window in OnSize because it is called by the framework when the DialogBox alone is created, before the edit is created.
So, you mean, even though it is virtual COM port, the DCB setting should also be set properly?
The reason I asked this question is that, someone actually told me that, if you are using virtual com port, you don't need to care about those settings. The only setting concerned is the COM port number.
This may or may not be true depending on the "virtual" COM port.
Sometimes USB devices register themselves as one or more COM ports and those could be called virtual. Different devices behave differently.
I've experienced USB devices used as COM ports that are "enabled" by setting the DTR line, which requires the use of DCB.
However, all COM devices should support the use of DCB, which means that it doesn't hurt to set up things properly. It would also make the code more portable between COM devices.
What you heard regarding not having to set the DCB for virtual COM ports may be true for some specific devices, but certainly not all.
It's supposed to be hard, otherwise anybody could do it!
Regarding CodeProject: "resistance is pointless; you will be assimilated"
Recently,I am writing a smtp server ,when I test it in the internet ,
I find that it can't send local email to other remote smtp server,
for example smtp.mail.yahoo.com etc.I don't know why?
Can anyone give me some advince?
I should know pointers by now but still struggle to get code working when dealing with them..
If anyone has any recommended articles I'd be very appreciative. But, the articles dealing with pointer basics don't seem to help me... not sure why. I can understand casting ints, etc. but when it gets to more complex data types, I get confused.
A good example of a tough pointer problem for me is seen below. Not sure why/where I'm reading/changing memory I shouldn't be and I also don't know how I would be able to get the value of the TextualSid in a format usable for strcmp, printf, etc.