C / C++ / MFC

30-Dec-06 5:40

The intellisense is not very safe... some times it disappears.

First of all copy the entire folder of the project as a backup.

If I do not remember it bad, you should close Visual Studio, delete the .clw file and then try to reopen that project and try to go to the class wizard, as it will fail to locate that file, then you'll be asked to generate it again.

Select all the files in that project again and then try it. The intellisense should work.

PS: I've been a lot of time without touching the Visual C++ environment so this is from some rusty place in my brain... please remember to make the backup previously.

Hope this helps.

Re: AMSEdit control

ErnestoNet30-Dec-06 6:17

ErnestoNet

30-Dec-06 6:17

Thanks for your fast response!!!!

Unfortunately, I'm using VS2005. There's no .clw file.

And the problem is exactly with that component.

I change the name from CAMSCurrencyEdit to CEdit, save the project, and the dialog appears in class view, I change it again to CEdit and it dissapears.

It's not a big deal, but it's annoying.

it´s the journey, not the destination that matters

Re: AMSEdit control

Joan M30-Dec-06 6:22

CString issue after upgrading to VS2005 (not using _T)

30-Dec-06 6:22

uuups... sorry, I'm beginning to be a dinosaur... Roll eyes | :rolleyes:

I hope to be able to switch to VS2005 this year 2007...

ErnestoNet wrote:
It's not a big deal, but it's annoying.

It always becomes annoying...

Well, I hope that somebody that will know better than me the VS2005 environment will be able to help you soon.

Good luck.

Error C2065

_tasleem30-Dec-06 4:35

_tasleem

30-Dec-06 4:35

hi i m using this code i on windows XP and visual studio 6,i receive error mentioned above
i had include these two lines as well,in stdaxh.h
#define _WIN32_WINNT 0x0500
#include <windows.h>
the code is below

<br />
MENUITEMINFO mii; <br />
memset(&mii, 0, sizeof(MENUITEMINFO));<br />
mii.cbSize = sizeof(MENUITEMINFO);<br />
mii.fMask = MIIM_ID| MIIM_BITMAP |MIIM_DAMFT_BITMAPTA; <br />

error is describled as below
D:\_RCProj\_VC6\live desktop\Source code\WinScreenAnotator.cpp(684) : error C2065: 'MIIM_BITMAP' : undeclared identifier
D:\_RCProj\_VC6\live desktop\Source code\WinScreenAnotator.cpp(684) : error C2065: 'MIIM_DAMFT_BITMAPTA' : undeclared identifier
Error executing cl.exe.
Creating browse info file...

WinScreenAnnotatorVC6.exe - 2 error(s), 0 warning(s)

Regards.
Tasleem Arif

Re: Error C2065

CPallini30-Dec-06 5:17

CPallini

30-Dec-06 5:17

well, MIIM_BITMAP is not defined in old versions of the winuser.h header file (maybe you'll need a Visula Studio service Pack, I'm not sure). On the other hand, I cannot find any reference to MIIM_DAMFT_BITMAP inside MSDN online, where did you get it?

If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.

Re: Error C2065

Hamid_RT30-Dec-06 5:45

Hamid_RT

30-Dec-06 5:45

It seems you need to include header file for 'MIIM_DAMFT_BITMAPTA'

WhiteSky

John Strudwick30-Dec-06 2:58

John Strudwick

30-Dec-06 2:58

Hi All

I have miles of old code that looks like this:
CString csString = "hello World";

Having just installed VS2005, I get the error:
'initializing' : cannot convert from 'const char [3]' to 'ATL::CStringT<basetype,stringtraits>

I know that I can get around this like this:
CString csString = _T("Hello World");

But want to know if there is a single switch somewhere that will let my code compile as it was?

I also don't understand why it's using ATL and not MFC - I craeted a new MFC project

Many thanks for any help offered

Re: CString issue after upgrading to VS2005 (not using _T)

Gary R. Wheeler30-Dec-06 3:11

30-Dec-06 3:11

John Strudwick wrote:
if there is a single switch somewhere that will let my code compile as it was?

Possibly; it sounds like you're set up for a UNICODE build. Take a look at your stdafx.h file. If the symbol UNICODE is #define'd, try commenting it out and rebuilding the solution.

John Strudwick wrote:
I also don't understand why it's using ATL and not MFC - I craeted a new MFC project

Back in MFC 7.0 (Visual Studio 2002) they switched from separate CString implementations within ATL and MFC to a single, common implementation. As part of that, they improved the type-safety of the various constructors and assignment operators.

Software Zen: delete this;

Re: CString issue after upgrading to VS2005 (not using _T)

John Strudwick30-Dec-06 3:15

John Strudwick

30-Dec-06 3:15

Thanks Gary - that has solved the problem
I went into the properties dialog and changed from unicode to not set - works a treat

Thanks again

Re: CString issue after upgrading to VS2005 (not using _T)

Gary R. Wheeler30-Dec-06 3:25

30-Dec-06 3:25

You're welcome. I believe I remember reading that the wizards in VS2005 changed from a default of building ANSI applications to UNICODE.

Believe it or not, there are advantages to building apps as UNICODE. They are much easier to translate to other languages (which may not be a concern for you). They also have something of a performance advantage. Windows itself uses UNICODE. With ANSI applications, there is an implicit conversion from ANSI strings to UNICODE with strings you pass to Windows, and the reverse when Windows returns strings to you.

Software Zen: delete this;

VC++6: Why KillTimer fails when I call it from PostNCDestroy

Joan M30-Dec-06 2:46

Re: VC++6: Why KillTimer fails when I call it from PostNCDestroy

30-Dec-06 2:46

and where should I call it?

Hello all,

in the PostNCDestroy overriden function of the main dialog I want to kill the timer that is running there, I'm calling something as simple as KillTimer(0); and this should work, but it makes the entire application to close suddenly.

Any idea?

Thank you in advance.

Gary R. Wheeler30-Dec-06 2:56

30-Dec-06 2:56

PostNcDestroy() is called after the corresponding window has been destroyed, which is why the KillTimer is failing. You don't need to call KillTimer in this case, because the window destruction takes care of it for you.

Software Zen: delete this;

Re: VC++6: Why KillTimer fails when I call it from PostNCDestroy

Joan M30-Dec-06 3:03

memory problems in borlandc 3.1

30-Dec-06 3:03

Thank you, I'll remove that commented line now.

crystalButterfly30-Dec-06 1:51

crystalButterfly

30-Dec-06 1:51

hi.I wanted to "benchmark" some sorting algorithms I learned from a book .
The problem is I cannot reserve into memory more than 16383 long variables.
That means 64kB .
I've made some research and understood that in real mode a segment is limited to 64 kB.I changed the compiling mode to large , but for nothing.

_/||||\_
/|- -|\
\--/

Re: memory problems in borlandc 3.1

Gary R. Wheeler30-Dec-06 3:04

30-Dec-06 3:04

It sounds like Borland C 3.1 is an MS-DOS compiler that generated 'real mode' executables. In real mode, no single data structure could be larger than 64K bytes. There were several memory models that specified the sizes of code and data supported. IIRC, the 'large' model specified code and data pointers that were four bytes; a two byte segment and a two byte offset. This let you have more than a total of 64K code and 64K data. Individual data elements (like your array) were still limited to 64K each, but you could have more than one of them.

There are more modern C and C++ compilers out there that are free for the download. Microsoft has Visual Studio 2005 C++ Express, I believe Borland makes a free version of their compiler available, and there's the open source 'gcc' compiler.

Software Zen: delete this;

Re: memory problems in borlandc 3.1

CPallini30-Dec-06 3:16

CPallini

30-Dec-06 3:16

Use another compiler... Smile | :)

If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.

Re: memory problems in borlandc 3.1

Paul Conrad30-Dec-06 13:11

Paul Conrad

30-Dec-06 13:11

CPallini wrote:
Use another compiler...

Exactly my thoughts Smile | :)

Debug Assertion Failed!-Combo Box- vc++ 8.

$uresh $hanmugam30-Dec-06 1:28

$uresh $hanmugam

30-Dec-06 1:28

Hi!

I have a few problems to add combo box within my dialog box and add the strings to that combobox using "AddString()" function within the "OnInitDialog()" function.

my coding like...

Cdialogex::OnInitDialog()
{

................
................

m_Combobox1.AddString("vc++");
.......................
......

}

Debug Assertion Failed!

Program: ...
File: f:\rtm\vctools\vc7libs\ship\atlmfc\include\afxwin1.inl
Line: 248

For information on how your program can cause an assertion failure, see the Visual C++ documentation on asserts.

But when i remove the code " m_Combobox1.AddString("vc++"); " ,program run successfully....
Now i am using VS. 8.0

Can anyone help me!!!

Re: Debug Assertion Failed!-Combo Box- vc++ 8.

Gary R. Wheeler30-Dec-06 3:20

30-Dec-06 3:20

Taking a guess, the m_Combobox1 variable isn't properly associated with a combobox control in the dialog. You can do this in one of two ways.

The first method: Add a combobox control to the dialog with the resource editor. In your OnInitDialog function, call m_Combobox1.SubclassDlgItem(IDC_MYCOMBOBOX,this);, where IDC_MYCOMBOBOX is the resource identifier for the control.

The second method: Create the combobox control directly:

CRect rect(10,10,100,200);
m_Combobox1.Create((WS_CHILD | WS_VISIBLE | WS_TABSTOP),
                   rect,
                   this,
                   IDC_MYCOMBOBOX);

rect is the location in the dialog where you want the combobox, and IDC_MYCOMBOBOX is the ID you want assigned to the control.

After you've done either of these, you can call the AddString method to add items to the control.

Software Zen: delete this;