|
It's having more than one function with the same name but with different argument types or number of arguments. Ideally the operations of each function should be similar in nature, for example two functions named Area where one might be for circles and another for cylinders. Each function takes different numbers of parameters, and the operations are not identical. If the operations were identical, with only the types of the arguments being different, then you would want to use a template function.
sf
|
|
|
|
|
I just upgraded to Visual C++ 2003, and haven't touched it yet. There is no book out that is MFC intensive in this new version. Has the MFC class structure changed greatly, or can I still rely on my huge MFC library of books that are VC 6.0 intensive?
sf
|
|
|
|
|
The MFC in VC7 is nearly identical to that in VC6. The biggest changes are under the hood and those are limited. The CString class, for example, is now shared with ATL and uses CStringT which is derived CSimpleStringT.
So, go ahead and use your huge library of MFC books.
Joe Woodbury
When all else fails, there's always delusion.
- Conan O'Brien
|
|
|
|
|
In the OnSize handler of my main window (CDialog) I am trying to reposition a listbox in my OnSize handler. I have the following code (I have stripped it down to what is still causing the crash. The assertion error only occurs when the window is first displayed.
void CDlg::OnSize(UINT nType, int cx, int cy) <br />
{<br />
m_ListBox.MoveWindow(10, 10, 50, 50, TRUE);<br />
CDialog::OnSize(nType, cx, cy);<br />
}
The error is an assertion failing in winocc.cpp:
void CWnd::MoveWindow(int x, int y, int nWidth, int nHeight, BOOL bRepaint)<br />
{<br />
ASSERT(::IsWindow(m_hWnd));<br />
<br />
if (m_pCtrlSite == NULL)<br />
::MoveWindow(m_hWnd, x, y, nWidth, nHeight, bRepaint);<br />
else<br />
m_pCtrlSite->MoveWindow(x, y, nWidth, nHeight, bRepaint);<br />
}
If I click "Ignore" when presented with the assertion error, execution continues just fine except that the listbox didn't get repositioned. On all subsequent OnSize calls, the listbox gets repositioned correctly.
Since I know the starting size of my dialog box, I can work around this by setting a flag so that during the initial OnSize call it won't reposition the listbox and I can just futz around in the resource editor trying to position it but it seems this isn't the right way to do this.
Can anyone help here?
|
|
|
|
|
Try adding:
if( m_ListBox.GetSafeHwnd() != NULL )
< code to move >
. . .
Guess I should explain why. the list box may not have the (as your seeing) a window handle (not created) and it is trying to move it.
Larry J. Siddens
Cornerstone Communications
TAME THE DOCUMENT MONSTER
www.unifier.biz
|
|
|
|
|
That is a better firewall than my BOOL kludge; flag 
But it makes me wonder - how do you position controls in a dialog if you can't position them until after they have been displayed in the wrong place?
|
|
|
|
|
If you manually call OnSize() from your OnInitDialog() (or OnCreate()) method, then they will be positioned correctly after they've been created in their initial positions.
To have them created initially in the correct place, either have them placed correctly in your dialog template, or create the controls in code instead of on a dialog template.
Shog9
nightdrivin'withoutheadlights...
|
|
|
|
|
I tried calling OnSize()manually from within my OnInitDialog() handler - both before and after CDialog::OnInitDialog() was called with the following:
BOOL CPeriodicTableDlg::OnInitDialog()
{
CDialog::OnInitDialog();
SetIcon(m_hIcon, TRUE);
SetIcon(m_hIcon, FALSE);
Table.InitGroups();
Table.InitElements();
m_SliderRed.SetRange (0, 255, TRUE);
m_SliderGreen.SetRange(0, 255, TRUE);
m_SliderBlue.SetRange (0, 255, TRUE);
m_GroupList.SetCurSel(0);
SetSliderPositions();
SetSliderValueText();
CRect r;
GetWindowRect(&r);
OnSize(SIZE_RESTORED, r.Width(), r.Height());
return TRUE;
}
and the app hangs. No errors, just an endless loop that I have to terminate with the Task Manager.
|
|
|
|
|
That's odd... Can you break into the debugger and see where it's hanging?
Oh, one thing - donno if this is it or not, but you don't need to call CDialog::OnSize() from within your handler - normally it does nothing useful, but in this case it may call Default() or something similar (can't remember of the top of my head) which could have unwanted results.
Shog9
nightdrivin'withoutheadlights...
|
|
|
|
|
I think the reason it happened is that, child controls are created after the parent window(your dialog) is created.
As soon as your dialog is created it will be sized to the initial dimensions thus a call to CDlg::OnSize() is issued right away. However, at this moment the child control has not been created yet, so you get an assertion falilure when you try to move that control since it's not a window yet. I think you should add a verification if (::IsWindow(m_ListBox.m_hWnd)) before calling m_ListBox.MoveWindow() and you should be OK.
|
|
|
|
|
Though the other answers give methods that will work and might be safer, I have always just checked the values of cx and cy. i.e.
void CDlg::OnSize(UINT nType, int cx, int cy) <br />
{<br />
if ( cx > 0 || cy > 0 )<br />
{<br />
m_ListBox.MoveWindow(10, 10, 50, 50, TRUE);<br />
}<br />
CDialog::OnSize(nType, cx, cy);<br />
}
which also does the trick.
|
|
|
|
|
Is there a way to free memory from struct?
|
|
|
|
|
Not sure what your asking...
If you allocated memory with "new", then use "delete" and set the pointer to NULL. If you did it with "malloc", then use "free" and set the pointer.
What you could do, is create a destructor for a struct and clean up there.
Example:
struct Stuff
{
Stuff() { p = NULL, i = 0; }
~Stuff() { delete [] p; p = NULL; }
int i;
char* p;
};
using:
{
Stuff x;
x.p = new char[10];
ASSERT( x.p );
x.i = 10;
< other usage >
} // cleanup, item will be destroyed.
Larry J. Siddens
Cornerstone Communications
TAME THE DOCUMENT MONSTER
www.unifier.biz
|
|
|
|
|
I just recently got back into C++ been a few years since I have done anyhting with C++ due to RL issues. I bought the book "C++ from the ground up" and it is using features I have never used before or seen and says these are now standard C++ features. So i googled and found that Visual Studio C++ does not work well at all with this new(to me atleast) standard. I was wondering if there is a update to Visual C++ to make it compliant with the standard C++ as that is what I want to learn. Oh I almost forgot I have version 6.0. All i have found is that it is all fixed in .net. Just trying to find out if there is a update to make it compliant with standard C++ features.
RanBlade
aka Eric Ranaldi
"Passion is what drive you to stay until 4am ficing that minor bug that hardly anyone would notice...Passion is where great games come from. If you don'l live and breath games, you shouldn't be in the gaming industry" - Dave Pottinger, Ensemble Studios
|
|
|
|
|
Not that I'm aware of. I'd love to see it but it ain't never going to happen.
MS only recently gave a rat's ass about C++ standards compliance recently and took onboard several high-profile C++ gurus.
"Sucks less" isn't progress - Kent Beck [^]
Awasu 1.1.2 [^]: A free RSS reader with support for Code Project.
|
|
|
|
|
So what compiler would you recommend to go with standard C++???
RanBlade
aka Eric Ranaldi
"Passion is what drive you to stay until 4am ficing that minor bug that hardly anyone would notice...Passion is where great games come from. If you don'l live and breath games, you shouldn't be in the gaming industry" - Dave Pottinger, Ensemble Studios
|
|
|
|
|
Is Visual C++.net compliant with Standard C++? or any of them ?
RanBlade
aka Eric Ranaldi
"Passion is what drive you to stay until 4am ficing that minor bug that hardly anyone would notice...Passion is where great games come from. If you don'l live and breath games, you shouldn't be in the gaming industry" - Dave Pottinger, Ensemble Studios
|
|
|
|
|
There are no 100%-compliant compilers, it's just a question of degree. VC7 is supposed to be significantly better than VC6 (which is not hard to do  ).
If you Google around, there are comparative reviews. The C++ Users Journal usually has good ones.
"Sucks less" isn't progress - Kent Beck [^]
Awasu 1.1.2 [^]: A free RSS reader with support for Code Project.
|
|
|
|
|
Visual C++ 7.1 is one of the most C++ standard compliant compilers available. It still lacks some of the more esoteric features, but the odds of you finding that to be a problem is extremely slim (moreover, most compilers aren't compliant with these features.)
Incidentally, VC++ 6.0 was fairly compliant. It did have problems with some template specifications like partial specialization, but it was still more compliant than many alternatives, all claims to the contrary.
In the meantime, it will take a while of learning C++ before you start stumbling with those parts of VC++ 6.0 that aren't compliant with the standard. Then you can move to VC++ 7.1. And if you want a compiler that is 100% compliant, forget it, one doesn't exist.
Joe Woodbury
When all else fails, there's always delusion.
- Conan O'Brien
|
|
|
|
|
Hello everyone
I'll try to explain what I want my program to do.
I'll use another program to make it easier to understand, let's say Microsoft Word.
So I minimize Microsoft Word and then run my program. Microsoft Word is running, but not active.
What I'd want my program to do, is to keep sending message strings to microsoft word.... let's say
hello [10 second pause]
world [10 second pause]
hello [10 second pause]
world [10 second pause]
and so on, while Microsoft Word is still minimized. And the program would stop sending strings to Microsoft Word until it's either stopped or paused.
Can anyone tell me how I could do this?
Thanks a lot,
~Michael
|
|
|
|
|
Lets see, how do I explain this. I need to read in a char and a double for each struct and print out its binary representation within that struct. For some reason when I read in the char and double for each struct all at once (like it is coded below) the binary representation gets messed up. If I only read in for one struct it seems to print out the binary rep. just fine, whether or not packed or unpacked.
There seems to be a memory problem when reading from all the structs at once.
Maybe one of you more experienced programmers can make some sense of this code and what might be the problem with printing out the binaries like they should be.
Thank you all for you help.
#include <stdio.h>
typedef unsigned int DWORD32;
#pragma pack(push,4)
typedef struct
{
char i;
double x;
}unPacked;
#pragma pack(pop)
typedef struct {
char i;
double x;
}packed_structure_t;
typedef struct
{
DWORD32
i :8,
x :23;
}bitField32;
void PrintBits(int size, unsigned char *bytes)
{
int j=0;
int on = 1;
int off = 0;
int t;
char *b = ((char *) &bytes);
int i;
for (i=0; i<size; ++i)
{
printf("\nByte%d ",j++);
for(t=7; t>=0; --t)
if(bytes[i] & (1 << t))
printf("%d",on);
else
printf("%d",off);
}
printf("\n\n");
}
int main(int argc, char *argv[])
{
bitField32 s;
unPacked n;
packed_structure_t p;
for(;;) {
int i;
double x;
printf("\n");
printf("Type in an int and a double: ");
scanf(" %d %lf", &i, &x);
printf("\n");
p.i=i;
p.x=x;
printf("Packed binary representation of a structure:\n");
PrintBits(sizeof(p),(unsigned char*)&p);
n.i=i;
n.x=x;
printf("Unpacked binary representation of a structure:\n");
PrintBits(sizeof(n),(unsigned char*)&n);
s.i=i;
s.x=x;
printf("Bit Field representation of a structure:\n");
PrintBits(sizeof(s),(unsigned char*)&s);
}
}
|
|
|
|
|
A double is 64 bits. A float is 32 bits.
Larry J. Siddens
Cornerstone Communications
TAME THE DOCUMENT MONSTER
www.unifier.biz
|
|
|
|
|
Yes, a double is 64 and a float is 32. And...?
|
|
|
|
|
Your bitfield is too small.
Larry J. Siddens
Cornerstone Communications
TAME THE DOCUMENT MONSTER
www.unifier.biz
|
|
|
|
|
Hi !
I have a small MFC SDI application, with "App -> Frame Window -> Form View" structure. Now, Form View has a member - a modeless dialog object. When the form view is created, it creates the modeless dialog, use it's controls, get stuff from there and so on.. Everything works fine..
But then, the PROBLEM
How can I access this very same modeless dialog from the Frame Window's level ? The modeless dialog is a child window of the Frame Window, but I have no clue about it's ID, which would be needed for CWnd::GetDescendant. I used the CDialog::Create with a resource ID to construct the dialog in the first place. So couldn't specify an ID there either.. Any clues on finding it ?
Greets,
Antti Keskinen
----------------------------------------------
The definition of impossible is strictly dependant
on what we think is possible.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
