|
Link statically. The problem will go away, forever.
|
|
|
|
|
Suppose I have a shortcut named "ABC" (let's say its object is "C:\Program Files\foo\bar.exe", which is not known at coding time), how do you get this shortcut's object path and name in your C++ code? Thanks.
|
|
|
|
|
I you do not mind COM, you could use IShellLink
|
|
|
|
|
Hi All,
I'm trying to do simple aplication to read data from the serial port and put it into an excel spreadsheet. Acctually I'm not sure about what should I use. I rather use VC++.
Could you give me just some advice to wich way should I go?
Thanks in advance,
Igor Kondrasovas
|
|
|
|
|
hi,
check this link, here the author is converting CSV to excel this might be of some help to u..
http://www.codeguru.com/mfc_database/CSpreadSheet.html
cheers..
Himanshu
|
|
|
|
|
You can find an easy start to Excel and ODBC here. Have a look!
|
|
|
|
|
The easiest would probably be an Excel VBScript "macro" using the MSComm object for reading from serial device. (It's amazing how much you can do in this crude language/environment...)
Another option would be generating a .csv file (Comma-separated Values), which excel tends to open nicely (if lannguage settings are correct)
Those who not hear the music think the dancers are mad. [sighist] [Agile Programming]
|
|
|
|
|
1.) CP has some great serial comm tutorials / classes / articles.
2.) you definately either want to write a dll or COM application and export your functions / interfaces for vb to use.
- I did something similar, i created a data aquisition application in VBA (Excel) that uses a dll i wrote in straight c. The dll is a socket client that connects to intelligent hardware and collects data. I had to reformat the data in the DLL so I could export it to excel, which was a bitch, but in the end it worked perfectly. You should have no trouble what so ever. If your going the DLL route, be sure to look into IDL.
Ryan Baillargeon
|
|
|
|
|
Is it possible to use MSComm object on .NET? I tried to convert an app from VB6 to .NET and I got erros, because the component could not be located...
Cheers
Igor
|
|
|
|
|
As it's a fairly "vanilla" COM object, it should work perfectly (just make sure it's registered on the system, and you added a reference to it to the project). I haven't tried it, though.
However, under .NET should be "more native" methods to talk to the serial port. No idea which, but would probably be worth doing (if you care about performance, or want to get rid of the mscomm.dll dependency)
Those who not hear the music think the dancers are mad. [sighist] [Agile Programming]
|
|
|
|
|
hi . i am searching for a Simple code to Show an Animated Gif in a Dialog Based Program or in a SDI project.
can anyone help me ? 
regards.
-=Ehsan-de-Burge=-
|
|
|
|
|
thanx for your responses 
|
|
|
|
|
dear all,
whenever i try to debug my vc 6 applications in windows Xp, i always get an error in MSDEV.exe (memory not read..)
why is it happening.
I can debug my applications in windows 98 and windows me .
why is it happenning!
any lights!!!!!!!!!!
thanx,
|
|
|
|
|
What SP release do you use?  With my XP everything worked fine with SP4, and after applying SP5, msdev started to crash from time to time - but rather at compile time than during debug.
Regards,
BB
|
|
|
|
|
which service pack- for xp or for visual studio.
anyways i use no service pack,
should i get one!!!!!
thanx
|
|
|
|
|
I meant Visual Studio SP4, but of course XP SPs are also recommended - I haven't noticed they would have messed something up. 
Regards,
BB
|
|
|
|
|
thanx for ur concern but even installing vs sp4, the problem persists,
now what should i do!
regards
|
|
|
|
|
If XP SPs also don't help, you may try a new clean installation 
Everything works fine for me.
Regards,
BB
|
|
|
|
|
Hello,
after closing my app. I can read some lines after Detected memory leaks!
an example:
Detected memory leaks!
Dumping objects ->
afxtempl.h(330) : {574839} normal block at 0x0191AAF8, 16 bytes long.
Data: < L_4 D > FF 7F 00 00 01 00 00 00 14 CB 4C 5F 34 96 44 06
afxtempl.h(330) : {574830} normal block at 0x019200E8, 64 bytes long.
Data: < L_ > FF 7F 00 00 00 00 00 00 14 CB 4C 5F DD 09 03 00
afxtempl.h(330) : {574821} normal block at 0x01912988, 64 bytes long.
Data: < L_ > FF 7F 00 00 00 00 00 00 14 CB 4C 5F DD 09 03 00
afxtempl.h(330) : {574812} normal block at 0x01919100, 64 bytes long.
Data: < L_ > FF 7F 00 00 00 00 00 00 14 CB 4C 5F DD 09 03 00
strcore.cpp(118) : {574811} normal block at 0x018F0118, 19 bytes long.
Data: < Past> 01 00 00 00 06 00 00 00 06 00 00 00 50 61 73 74
strcore.cpp(118) : {574810} normal block at 0x019202C0, 18 bytes long.
Data: < Agua> 01 00 00 00 05 00 00 00 05 00 00 00 41 67 75 61
strcore.cpp(118) : {574809} normal block at 0x0192ECD0, 18 bytes long.
...
how can I get the origin of them?
as always thank you in advance...
|
|
|
|
|
Usually, you can just doubleclick on the line, as you would with a build time error, but it tends to be awkward with strings, as it just gives you a reference to where the string itself allocated the memory (which isn't useful to you)
However, you can see part of the string that was allocated "Past" and "Aqua" so that should make it possible for you to work out where the strings were allocated
--
Help me! I'm turning into a grapefruit!
|
|
|
|
|
ok...
I'll try to find it...
but I'm using CString object in order to handle my strings. Do I need to release in some way the string?
Thank you in advance.
|
|
|
|
|
Do you cast your CStrings into LPTSTR instead of LPCTSTR somewhere?
That is, do you bend them into being non-const?
Or do you GetBuffer() somewhere without Release()?
Release() is only needed after GetBuffer(), but then ABSOLUTELY needed.
Normaly, the CString is dealocated when it goes out of scope.
My opinions may have changed, but not the fact that I am right.
|
|
|
|
|
 ;)hi,
read memory contents at
0x0191AAF8
0x019200E8
0x01912988
.
.
.
in the files as shown as see where you get, i guess maybe you are allocating some memory and not releasing it out afterwards. just check out...I m not sure whether i am right or not..did it a yr ago i guess.
cheers
Himanshu
|
|
|
|
|
Since you are using MFC, put the following code at the top of each source file in your program (after the #includes):
#ifdef _DEBUG
#define new DEBUG_NEW
#undef THIS_FILE
static char THIS_FILE[] = __FILE__;
#endif
Then, when you get these memory leaks, you will be able to see the location where you allocate the object that you are leaking.
Note that it's possible to do this even if you don't use MFC, but then you have to write your own new and delete operators, and I don't want to explain all that.
Chris Richardson
Programmers find all sorts of ingenious ways to screw ourselves over. - Tim Smith
|
|
|
|
|
Thank you for the information, I've located them before, but this is a good point...
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
