here, the first operand has the side effect of calling getnextthingie and assigning the result to c. c!=EOF is evaluated as loop condition.
Personally, I love the idea that Raymond spends his nights posting bad regexs to mailing lists under the pseudonym of Jane Smith. He'd be like a super hero, only more nerdy and less useful. [Trevel] | FoldWithUs! | sighist | µLaunch - program launcher for server core and hyper-v server
I am using main "standard" property sheets for tabbed application.
I would like to have another property sheet embedded in the main tab(s).
I got as far as using CStatic variable in the page, but now I am stuck.
I tried this (snippet)
position = pDoc->GetFirstViewPosition();
COpenHRView *pOpenHR = (COpenHRView*) pDoc->GetNextView(position);
m_sstv.Detach(); // added this when Attach asserted – no go asserts
m_sstv.Attach(pOpenHR->m_pPropFrame1->GetSafeHwnd()); // asserts– attach only once
Thanks for reading. Any constructive help as always is appreciated.
But the Problem is, that I get the current size of my form with GetWindowRect(). If it has already been scaled to small, some of the form controls will not be shown...I need the height and width of my Form as I see it in the form Editor...
One way I could think is store your original dialog rectangle in some variable and use those values in InitDialog() Function. The other dirty way, you can check the the dialog box co-ordinates in .rc file. and set the Dialogbox rectangle to those value in InitDilaog fuction().
The easy answer is: you don't have to convert, just assign it. But it depends on your UNICODE setting. I suggest you read this article[^] to get a better understanding on character encodings. This will help you a lot in the future.
As I said in my previous reply, it all depends on your UNICODE setting.
BTW, why don't you just check ? It's one line of code and you can easily verify if it compiles or not. If UNICODE is turned on, the code won't compile.
Just be carefull, your char array has to be null-terminated to be used to initialize a CString like that or even if you use the = operator ( CString str; str = charr; ). Othwerwise it will keep on reading characters till it finds a null character somewhere after your array and which either results in access violation OR you get garbage in your str.
> The problem with computers is that they do what you tell them to do and not what you want them to do. < > Sometimes you just have to hate coding to do it well. <
Last Visit: 1-Dec-20 13:52 Last Update: 1-Dec-20 13:52