C / C++ / MFC

Steve Echols7-Dec-06 12:07

Steve Echols

7-Dec-06 12:07

Do you mean drop the list down programatically?

m_open.ShowDropDown( TRUE );

- S
50 cups of coffee and you know it's on!

celllllllll7-Dec-06 12:27

celllllllll

7-Dec-06 12:27

no...not programatically.....but its default. Like when I type m_open.

After "." it should open me a drop down list and we can select anything. For example "IsWindowEnabled". And then I won't have to type it, I can select and then press ENTER.

I hope I explained it now.
Thanks

C++Prog

Steve Echols7-Dec-06 12:33

Steve Echols

7-Dec-06 12:33

Ah, you mean Intellisense. It's touch and go for me on VC6 - sometimes I get it, sometimes I don't. I have no idea what breaks it.

- S
50 cups of coffee and you know it's on!

celllllllll7-Dec-06 12:39

celllllllll

7-Dec-06 12:39

O okay....but thanks anyways for telling me what is it called..Smile.

Intellisense..now will remember it.

Thanks

C++Prog

Mark Salsbery7-Dec-06 12:43

Mark Salsbery

7-Dec-06 12:43

First make sure that the variable's type is known (as seen by the compiler) at the point
you are typing. If the variable isn't already defined then intellisense won't know what to put
in the list.

If that doesn't work then possibly the intellisense database is corrupt (that's been happening
for many VS versions Smile | :)

). To rebuild the intellisense database:
1) Exit VS or at least close the project/solution.
2) Find the <solutionname>.ncb file in your solution/project folder.
3) Rename it to something like <solutionname>_bak.ncb if you want to be safe Wink | ;)

4) If you didn't rename it then delete it.
5) Open the project/solution in VS and a new .ncb file will be built

celllllllll7-Dec-06 13:05

celllllllll

7-Dec-06 13:05

How would I make sure that the variable type is known at the point of typing?

I rebuilded the .ncb file but that doesn't work.

Thanks for your effort.

C++Prog

Mark Salsbery7-Dec-06 13:13

Mark Salsbery

7-Dec-06 13:13

celllllllll wrote:
How would I make sure that the variable type is known at the point of typing?

Just like the compiler sees it - startin at the top, through all include files and their included
files.

If I just start typing:

myvariable.

Intellisense knows nothing.

If I type:

CWnd myvariable;
myvariable.

Intellisense gives me the list of CWnd members, assuming somewhere above these lines I have
included the header file declaring the CWnd class.

p.s.
I still kind of chuckle every time I type the word "Intellisense", considering it is the #1 problem
I've had over the years with VS Smile | :)

*edit* One other thing - Intellisense has always started working again at some point for me Laugh | :laugh:

Mark Salsbery7-Dec-06 13:19

Mark Salsbery

7-Dec-06 13:19

Ah shoot - I said "one other thing" - I lied.

Also, if there's a coding error above the line you're typing and intellisense can't parse through
the error then it will stop working as well. So, sometimes compiling (if the error isn't obvious)
will show you where it's getting hung up.

Mark

David Crow8-Dec-06 4:29

8-Dec-06 4:29

celllllllll wrote:
How would I make sure that the variable type is known at the point of typing?

It will also fail to work if you are in a method that has not yet been added to the class' .h file.

"Approved Workmen Are Not Ashamed" - 2 Timothy 2:15

"Judge not by the eye but by the heart." - Native American Proverb

ODBC question

Jim Crafton7-Dec-06 10:28

Jim Crafton

7-Dec-06 10:28

Let's say I have a generic interface for DB access. If I use ADO to implement this interface, can this wrapper also be said to support ODBC on Windows? Or do I need to write another implementation for ODBC using the SQLXXX Win32/ODBC API functions?

¡El diablo está en mis pantalones! ¡Mire, mire!

Real Mentats use only 100% pure, unfooled around with Sapho Juice(tm)!

SELECT * FROM User WHERE Clue > 0
0 rows returned

Save an Orange - Use the VCF!
Techno Silliness

Re: ODBC question

Jörgen Sigvardsson7-Dec-06 12:19

Jörgen Sigvardsson

7-Dec-06 12:19

I don't see how. ODBC is a set of functions split on two interfaces (interface in the general sense, not the COM way): one for the database client and one for the database provider. Unless there are some magic ADO->ODBC adapters (I know of none - but on the other hand I do not claim that I know everything Wink | ;)

), I don't see how ADO could ever provide any data for ODBC clients.

--
In Hypno-Vision

Re: ODBC question

S Douglas9-Dec-06 0:19

S Douglas

9-Dec-06 0:19

Jim Crafton wrote:
If I use ADO to implement this interface, can this wrapper also be said to support ODBC on Windows?

Absolutly, ADO can connect to an amazing number of data sources. The best place to go to find out how to connect to different datasources is http://www.connectionstrings.com/[^]. Biggest chanlenge is supporting all of the various SQL differences out there.

I'd love to help, but unfortunatley I have prior commitments monitoring the length of my grass. :Andrew Bleakley:

C++ and VB.NET

Kornfeld Eliyahu Peter7-Dec-06 9:31

7-Dec-06 9:31

Hi,

I have a VC++/MFC application.
I decided to move the UI to VB.NET to improve it.
I created a VB project with new interface and moved the C++ core into a MFC dll project.
When I run the application I got 'Stack owerflow' inside the MFC code.

For code details:
The C++ code does image processing using some recursive functionality, that is the point where the stack sucks up.
It happens when I passing over 4400 iterrations (the maximum is about 12000).

The recursive function looks like this

<br />
// Check for continous black areas<br />
void CBitmapScan::CheckAround(CRect* pBound, int nX, int nY)<br />
{<br />
	if(oMemDC.GetPixel(nX, nY) == RGB(0x00, 0x00, 0x00))<br />
	{<br />
		// Remove the pixel to avoid duble-check<br />
		oMemDC.SetPixel(nX, nY, RGB(0xff, 0xff, 0xff));<br />
<br />
		// Set new bounds<br />
		if(pBound->left > nX) pBound->left = nX;<br />
		if(pBound->right < nX) pBound->right = nX;<br />
		if(pBound->top > nY) pBound->top = nY;<br />
		if(pBound->bottom < nY) pBound->bottom = nY;<br />
<br />
		// Check up-down-left-right<br />
		CheckAround(pBound, nX + 1, nY);<br />
		CheckAround(pBound, nX - 1, nY);<br />
		CheckAround(pBound, nX, nY + 1);<br />
		CheckAround(pBound, nX, nY - 1);<br />
	}<br />
}<br />

Why this happening?!

Thanks in advance

Peter

zoid ! 7-Dec-06 10:55

zoid !

7-Dec-06 10:55

Your recursive function does not seem to have any terminating condition, so your recursion is infinite.

you might want to look at your logic here:

CheckAround(pBound, nX + 1, nY);
CheckAround(pBound, nX - 1, nY);

The function will keep bouncing back and forth between those two pixels under some conditions.

Kornfeld Eliyahu Peter7-Dec-06 12:09

7-Dec-06 12:09

Actualy the terminating condition is in the first line of the function!

If it finds a black point IT REMOVES IT than moves over.
So never will jump back and forth because the first point already removed!

Zac Howland7-Dec-06 11:51

Zac Howland

7-Dec-06 11:51

Kornfeld Eliyahu Peter wrote:
void CBitmapScan::CheckAround(CRect* pBound, int nX, int nY)
{
if(oMemDC.GetPixel(nX, nY) == RGB(0x00, 0x00, 0x00))
{
// Remove the pixel to avoid duble-check
oMemDC.SetPixel(nX, nY, RGB(0xff, 0xff, 0xff));

// Set new bounds
if(pBound->left > nX) pBound->left = nX;
if(pBound->right < nX) pBound->right = nX;
if(pBound->top > nY) pBound->top = nY;
if(pBound->bottom < nY) pBound->bottom = nY;

// Check up-down-left-right
CheckAround(pBound, nX + 1, nY);
CheckAround(pBound, nX - 1, nY);
CheckAround(pBound, nX, nY + 1);
CheckAround(pBound, nX, nY - 1);
}
}

You aren't checking to see if nX (nor nY) are within your current bounds before your recursive calls. Thus, the first recursive call will be called infinitely many times (and the subsequent ones will never get called, but would also be infinte if they were called).

If you decide to become a software engineer, you are signing up to have a 1/2" piece of silicon tell you exactly how stupid you really are for 8 hours a day, 5 days a week

Zac

Kornfeld Eliyahu Peter7-Dec-06 12:15

7-Dec-06 12:15

You right, however I have not to do because for every out-of-bound cordinates GetPixel returns -1, and that value will terminate the current run.

As you see the function actualy called only about 4500 times when the 'stack overflow' occured.
And more this function WORKS in a pure VC++ environment, only the in combination with the VB.NET interface it fails!

Kornfeld Eliyahu Peter8-Dec-06 2:41

"Encountered problem" message when closing

8-Dec-06 2:41

I have a solution to this problem.

I enclosed the functionality inside a new thread with a large stack and everything goes well.
The question remains is how to enlarge the stack for a VB.NET project?

acerunner3167-Dec-06 9:14

acerunner316

7-Dec-06 9:14

I have a dialog based program using MFC. The program runs as expected when its opened. But when I close the dialog box (clicking the "X" or "esc"), I get the windows message "Program encountered an error and needs to be closed. We are sorry for the inconvenience." and askes to send error report. This happens almost every time I try to close. Since this is occuring only when closing, I have no idea how to debug this. Can anyone help? What could possibly be causing this?

David Crow7-Dec-06 9:29

Re: "Encountered problem" message when closing [modified]

7-Dec-06 9:29

What is the program doing when it closes? Are you able to comment out all nonessential code and still reproduce the problem? Does this happen in debug or relase mode, or both?

"Approved Workmen Are Not Ashamed" - 2 Timothy 2:15

"Judge not by the eye but by the heart." - Native American Proverb

acerunner3167-Dec-06 9:51

acerunner316

7-Dec-06 9:51

Just looking at the OnCancel() function, all I do is call a function that closes a driver (my program uses SDK provided to access drivers).

I also deallocate a pointer to an array if its allocated.
if (ptrArray)
{
delete []ptrArray;
ptrArray = 0;
}

I thought this might be causing a problem, but I've had the "encountered problem" message before I put this code in.

It occurs in both debug and release mode.

David Crow7-Dec-06 10:14

7-Dec-06 10:14

acerunner316 wrote:
It occurs in both debug...

So what happens if you start the program using F5 (instead of Ctrl+F5)? Do you get any useful text in the debug window?

"Approved Workmen Are Not Ashamed" - 2 Timothy 2:15

"Judge not by the eye but by the heart." - Native American Proverb

acerunner3167-Dec-06 10:41

acerunner316

7-Dec-06 10:41

I get this sometimes

HEAP[<my_program_name>.exe]: Invalid Address specified to RtlFreeHeap( 00390000, 0010F57C )

or sometimes i get

The program <my_program_name>.exe exited with code 0x2

I guess I should also note that I don't really know how to use the debugger. I'm a Visual C++ noob. I only use debug and release to check that my code works the same on both, and works as expected.

David Crow7-Dec-06 10:58