|
Hi,
I haven't used the MFC classes in nearly a decade but maybe I can help you debug it.
kittmaster wrote: but it "leaves behind" the a non functional version of the floating toolbar where it was once docked.
My instincts are telling me that the non-client area[^] has expanded down when your CControlBar was created.
Can you check for this for me? You can get the non-client area by calling GetWindowRect [^] and subtracting the GetClientRect[^].
If I am correct then you will need to send the WM_NCCALCSIZE message[^] to reclaim your top client area.
Best Wishes,
-David Delaune
|
|
|
|
|
|
Well,
Your Debug window is showing a 39 pixel difference on the Y axis, so the client area size has certainly changed.
Go through the CControlBar documentation to make sure there isn't a built-in way to avoid the non-client area resizing. I don't remember off the top of my head.
If not then maybe use a sledge hammer to fix it by sending a WM_NCCALCSIZE to resize it manually.
Best Wishes,
-David Delaune
|
|
|
|
|
I added this line of code after the difference calculation:
AdjustWindowRectEx(&rect, m_wndToolBar.GetStyle(), FALSE, m_wndToolBar.GetExStyle());
It zeroed out the values but the same ghost blocks still remain. I can't find direct access to that variable you mentioned, any code example/tips you could point me to?
Thanks,
Chris
|
|
|
|
|
|
I found that via the class I was looking at and reading the class methods when we were looking at the rectangle offsets. I read it as it would recalc the rectangles of the toolbar and plant it, clearly I was incorrect as my result are as you mentioned...not working.
I will look at the code samples you linked to.
Thank you,
Chris
|
|
|
|
|
To check given string is Palindrome or not in Mfc c++
|
|
|
|
|
I see your randomness and raise you, "The golf course maintains a luxury garden or not." 
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"You can easily judge the character of a man by how he treats those who can do nothing for him." - James D. Miles
|
|
|
|
|
It isn't really specific of MFC.
Let's say you have a string s with length L, then you just need to check if (s[i] == s[L-1-i]) evaluates true for every i in the 0, .., (L/2) range.
"In testa che avete, Signor di Ceprano?"
-- Rigoletto
|
|
|
|
|
|
|
No.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
First, the assignment is incomplete as you tried to post the entire thing in the subject line instead of the body of the post.
Second, no, we're not here to do your work for you. Asking for such is insulting.
If you've got questions about your your own code, fine, we can help with that, but you have to ask the questions with proper detail to answer them.
|
|
|
|
|
Does it even matter?
I suppose if you need something uniquely implemented in the new SDK, you're want to build/link against it. But if you have a basic app, why worry about it?
As a rule, do you just keep your SDK on your machine current to the latest from Microsoft?
thx
Charlie Gilley
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
Has never been more appropriate.
|
|
|
|
|
Whatever gets installed along with Visual Studio and the compilers works for me.
|
|
|
|
|
My perception as well.
Context: so I typically have one development machine for about 4 years. The one I'm typing on is 5+ years old (dang, I need to replace). So what happens over that period of time is that I collect SDKs. I don't pay attention. But I'm trying to position code I need in a "highly secure environment" - which means its elephanting impossible to get any work done, but the IT guy promises to install what I request.
Charlie Gilley
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
Has never been more appropriate.
|
|
|
|
|
turns out cleaning up after using a linked list isn`t as simple as I thought.
I know this is wrong but it`s the best code I was able to come up with. Any help for setting me on the correct path is appreciated.
void CleanUp(SomeNode * FrontTip)
{
SomeNode * Temp;
Temp = (SomeNode*)malloc(sizeof(SomeNode));
while(FrontTip->next != NULL)
{
Temp = FrontTip;
FrontTip = Temp->next;
free(Temp);
}
}
|
|
|
|
|
You don't need to malloc Temp: it's just a pointer. You also forgot to free it. You also didn't free the FrontTip argument if it's the only thing allocated (i.e. if its next is NULL). I would write
while(FrontTip != NULL)
{
SomeNode* Temp = FrontTip->next;
free(FrontTip);
FrontTip = Temp;
}
|
|
|
|
|
Quote: You don't need to malloc Temp: it's just a pointer.
I couldn`t explain that bit myself either, it was probably serving for a different purpose in the article I was learning from.
Thanks for your version and your help.
modified 22-Mar-22 18:39pm.
|
|
|
|
|
To be specific about what @k5054 wrote, use std::unique_ptr[^] whenever possible. There's also shared_ptr and weak_ptr for a pointer with multiple owners (shared) or users (weak).
|
|
|
|
|
Hey Greg, there`s more than one issue in the function I posted. Like how do you go about managing a pointer that has been passed to the function.
I`ve seen this code in a codeproject article:
void NukeA(A* p)
{
p->DoThis();
p->DoThat();
delete p;
p = nullptr;
}
My thought is that this is wrong because the original pointer (the pointer being passed) remains at the gates of the function unaffected by the changes inside NukeA();
void NukeSafelyA(A** p)
{
(*p)->DoThis();
(*p)->DoThat();
delete *p;
*p = nullptr;
}
My question is how do you go about assigning a pointer to the pointer being passed or assign the pointer being passed to a new pointer that is stated/declared in the body of the function;
void NukeSafelyA(A** p)
{
(*p)->DoThis();
(*p)->DoThat();
A * Temp1;
A * Temp2;
(*p) = Temp1;
Temp2 = (*p);
delete *p;
*p = nullptr;
}
modified 24-Mar-22 12:13pm.
|
|
|
|
|
Setting a pointer to nullptr after invoking delete on it is definitely recommended. Or in C, setting it to NULL after invoking free. To do it, pass the pointer by reference:
void NukeSafelyA(A*& p)
{
p->DoThis();
p->DoThat();
delete p;
p = nullptr;
}
|
|
|
|
|
Us old-school C programmers tend to forget about the existence of references. Well done, Greg. That's far cleaner than the pointer-to-pointer version the OP presented, but does exactly the same thing.
To the OP:
On the whole though, except as a learning exercise, and some really rare, odd cases, the STL should be the way to go. It's likely to be safer, perhaps faster, and certainly far better tested than your own implementation. The STL should be part of your basic tool kit for C++ programming.
Keep Calm and Carry On
|
|
|
|
|
Thanks guys. As you lean stuff, you begin to understand things that you previously heard about but never really understood. I`m taking the std pointers as a new horizon, at this point I feel that they are remote from where I am. I`ll be using the default c++ approach.
|
|
|
|
|
I am using a property sheet for my app to adjust the options and GUI elements. When the file opens, the app has two tabs created via Addview and all of that is working. OnInitialUpdate sets the styles because it uses the registry settings when it starts. What I'm trying to do is have the styles adjust on an OnApply when the user selects the style they want. I have the OutputPane working correctly which is shown in the code below. What I can't get to work is to have the document tabs change on a Recalc/Redraw.
BOOL CSettingsUserTabs::OnApply()
{
BOOL bResult = CMFCPropertyPage::OnApply();
if (bResult)
{
AfxGetApp()->WriteProfileInt(_T("Settings"), _T("UserTabStyle"), m_style_tabs);
((CMainFrame*)AfxGetMainWnd())->m_wndOutput.m_wndTabs.ModifyTabStyle((CMFCTabCtrl::Style)m_style_tabs);
((CMainFrame*)AfxGetMainWnd())->m_wndOutput.m_wndTabs.RecalcLayout();
CMFCTabCtrl& MDI_STYLES = ((CMainFrame*)AfxGetMainWnd())->GetMDITabs();
MDI_STYLES.ModifyTabStyle((CMFCTabCtrl::Style)m_style_tabs);
MDI_STYLES.RecalcLayout();
CMDIFrameWndEx* pMainFrame = DYNAMIC_DOWNCAST(CMDIFrameWndEx, GetTopLevelFrame());
pMainFrame->SetFocus();
pMainFrame->RecalcLayout();
}
return bResult;
}
Any ideas what I can do solve this problem? I've scoured the net for examples on how to solve this issue and yet to get it to work. There is a TabControl solution in the Microsoft master repository to show how it works, but since I'm using a propertysheet to control it, the example does work but the example doesn't use the AddView so I can't use it as a good example.
Here is the code that loads the RUNTIME_CLASSES where the tabs are created:
void CMovieView::OnInitialUpdate()
{
AddView(RUNTIME_CLASS(CTabView1), AfxStringID(IDS_TAB1));
AddView(RUNTIME_CLASS(CTabView2), AfxStringID(IDS_TAB2));
GetTabControl().EnableTabSwap(TRUE);
GetTabControl().SetLocation(CMFCBaseTabCtrl::Location::LOCATION_TOP);
GetTabControl().EnableAutoColor(TRUE);
int UserTabStyle = AfxGetApp()->GetProfileInt(_T("Settings"), _T("UserTabStyle"), 0);
if (UserTabStyle != FALSE && UserTabStyle <= 8) {
int EnumUserTabStyle = UserTabStyle - 1;
GetTabControl().ModifyTabStyle(static_cast<CMFCTabCtrl::Style>(EnumUserTabStyle));
}
else {
GetTabControl().ModifyTabStyle(CMFCTabCtrl::STYLE_FLAT);
}
CTabView::OnInitialUpdate();
}
This works on creation, I can't get it to work when the OnApply() is used because you can't recall OnInitialUpdate for something already created. I can't seem to get GetTabControl() to work after on create as a separate function....so I'm unclear on how to solve this problem. Does anyone have any ideas on how I can modify my code to get it working?
Thanks,
Chris
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
