|
okey, runned new check and it still works
thanks again
|
|
|
|
|
Glad i could help, but i am not sure how safe this solution is...i am not sure what exactly the hInstance is used for when you register a custom control, i guess it is used by the system to automatically unregister window classes when the module that contains their implementation gets unloaded, if it is so, then as long as your DLL is in memory while your program runs you should not run into any troubles, however i do not know when that DLL will get unloaded, if you still have such custom controls hanging around windows when your DLL is unloaded you probably will run into problems...or i am just being too cautious about it. Anyways, good luck.
> The problem with computers is that they do what you tell them to do and not what you want them to do. <
> Life: great graphics, but the gameplay sux. <
|
|
|
|
|
Hi to all,
I am a new learner in visual C++ 6.....I knew C++ language, and now i learnt visual studio editor also....just what is enough to debug and run the project...
Now i am having free time and I would like to learn more...I want to be a good vc6 programmer.
Could anyone please suggest some topics(may be related to project design, C++ Concept or anything in VS6 editor that one should know) to me so that I can go through.
Thanks in advance.
-----------------------------
I am a beginner
|
|
|
|
|
your problem is too brief can u explain it little more... what type of programs you want to make in VC++6.
|
|
|
|
|
right now am working on console based application only....
-----------------------------
I am a beginner
|
|
|
|
|
It sounds as though you are interested in making GUI applications. Is that correct?
"Old age is like a bank account. You withdraw later in life what you have deposited along the way." - Unknown
"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
|
|
|
|
|
i have work in win32 console base application project...also i tried GUI(MFC) of my own....i mean i have very basics of MFC.....so it will be great if u send some topic in console based application...mFC also would be additional knowledge for me
-----------------------------
I am a beginner
|
|
|
|
|
The next step after console applications is using windows for your GUI. There are two approaches you can take: 1. Classic MFC and 2. .NET.
.NET is more modern (and both easier to use and more powerful) but isn't supported in your compiler version (VS 6). If you can get a copy of the Scribble Tutorial (Microsoft), it's a good, simple introduction to MFC.
Effective C++ by Scott Meyers is a good way to extend your C++ skills. Design Patterns by Gamma et al teaches you how to apply the object-oriented features you've learned to solve practical problems.
|
|
|
|
|
Thanks a lot....I will go through all this concepts
-----------------------------
I am a beginner
|
|
|
|
|
|
Thanks you sir, for the precious reply
-----------------------------
I am a beginner
|
|
|
|
|
My Visual studio debug sessions are suddenly behaving erratically. The debugger position does not correspond with the c++ source code line, it's sometimes one line off. This used to work fine. I'm VS 2005 SP1. Any ideas what might be wrong?
|
|
|
|
|
Hi,
I am just giving a try....
May be your exe hasn't been updated, with the current code and debugging points.Its a old one
What you can do is,
- check the exe path in project settings...see if it is existing, check the updated time(after re-building)
- or, delete the exe...rebuild the project..if no new exe has been updated to that path, that means your path is wrong....
-----------------------------
I am a beginner
|
|
|
|
|
No, that's not it. I'm just going to try to reinstall and see if that does the trick.
|
|
|
|
|
fine, hope it works fine....if that doesnot work....just try this one....coz even I had the same problem...
-----------------------------
I am a beginner
|
|
|
|
|
Have you removed all temporary files, including the Debug folder, and rebuilt the project?
"Old age is like a bank account. You withdraw later in life what you have deposited along the way." - Unknown
"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
|
|
|
|
|
|
What about optimizations?
"Old age is like a bank account. You withdraw later in life what you have deposited along the way." - Unknown
"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
|
|
|
|
|
This may be too simple a solution but what you describe usually occurs when you start debugging a release version.
Is your active configuration 'Debug' ?
Souldrift
modified on Monday, August 24, 2009 9:53 AM
|
|
|
|
|
Yes, I know about that, but it's definately debug version
|
|
|
|
|
The standard solution to this problem is to select "Rebuild Solution" in Visual Studio. Sometimes the source gets out of sync with the stored debugging information, and Rebuild Solution brings it up to date.
|
|
|
|
|
Yeah, that's the first thing I tried. But I notice when I moved the function that I was debugging to a different position in the file that the problem went away. Seems like VS just doesn't like my source code
|
|
|
|
|
hi,
it may be cause of fault in encoding of lines endings in Your source file, ie. from any reason at end of line instead of standard windows CRLF code ('\x0D','\x0A') appear the CR code ('\x0D'). Debugger counts line endings and if any encoding of line end differs from the other it may results in wrong line highlighting. To eliminate this problem You can use any text tool that can re-encode the line endings in Your source file to standard windows encoding or You can use Visual Studio editor feature "Save With Encoding" into "Save File As..." dialog. I would try first in VS do "Save File As..." -> Unix/Macintosh and next "Save File As..." -> Windows.
modified on Tuesday, August 25, 2009 9:28 AM
|
|
|
|
|
You know I have a switch statement like this:
switch (keyCode)
{
case 0x10:
maybe it's somehow recognising the 0x10 as a new line return. That makes sense becuase it's only after this switch statement that the error occurs
|
|
|
|
|
ed welch wrote: You know I have a switch statement like this:
switch (keyCode)
{
case 0x10:
maybe it's somehow recognising the 0x10 as a new line return.
No, not possible.
"Old age is like a bank account. You withdraw later in life what you have deposited along the way." - Unknown
"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
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
