|
hi Shaw
I know MFC is simply a wrapper for WIN32 API. if i want to code win32 app. i have to learn pure win32 coding without any choice.
۞It is on our failures that we base a new and different and better success.
|
|
|
|
|
The main function (routine/method/what ever...) is the entery point in both C and C++. It is when we need to run it in an eniroment like Windows, Lenux, or Apple (Macintosh) that we have problems.
Until you understand the basics, stick to console programes. That is programes that require a main() routine.
INTP
Every thing is relative...
|
|
|
|
|
Nguyen Thi Thanh wrote: Can you help me. Thank you.
this section of codeproject is full of beginner tutorial.. i believe it will help... just follow this link
http://www.codeproject.com/cpp[^]
"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow
cheers,
Alok Gupta
VC Forum Q&A :- I/ IV
|
|
|
|
|
ex.
z:\windows\explorer.exe
|
|
|
|
|
hi "HOW"
well to me path is whole location of a file
eg. z:\windows\explorer.exe
Directory is a folder and we store files in folder.
eg. windows is a folder
filename is the name of a file.
eg. explorer.exe is a binary file
To access a file we must have complete file path
good luck!
۞It is on our failures that we base a new and different and better success.
|
|
|
|
|
tx, LivingThoughts
z:\windows\explorer.exe == path?
z:\windows == path?
z:\windows == ?
directory == folder ?
z:\windows == directory ?
z:\windows == folder ?
|
|
|
|
|
HOW WHAT wrote: z:\windows\explorer.exe
Let me break every thing to simplify every thing for you
z: = PATH and Drive Name
Z:\Windows :- Path and Directory
Z:\Windows\explorer.exe :- path and Filename
Path can be any thing.. but it depends on what you are calling
"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow
cheers,
Alok Gupta
VC Forum Q&A :- I/ IV
|
|
|
|
|
Hello everyone! 
Alright... Remember the questions about binary files I've been asking lately? Well, thanks to you, my program worked! 
I converted the program to C (not C++), no problem... I added a file header at the beginning of file, no problem... but if I try to compile the program with the Digital Mars compiler, with the -mtd option (DOS .COM file), and I make a file with that program, the file comes out 10 bytes less than the Windows version! Therefore, the programs can't open each other's files! Anyone know of a solution?  Thanks!
PS: In case you need the code to help me out, here it is: (233 lines)
http://sulfurmidis.com/peopledb.htm[^]
Lord Kixdemp
www.SulfurMidis.com
www.SulfurSoft.tk
[ftp://][http://][hotline://]tsfc.ath.cx
-- modified at 18:21 Sunday 12th February, 2006
|
|
|
|
|
Have you compared the 2 output files? If it's only 10 bytes, you should be able to find the differences easily 
|
|
|
|
|
Well... based on the error messages I get, the headers are messed up... Why isn't there a native DOS version of GCC?! (One that doesn't need a cwdpmi server or whatever it's called...)
Anyways... I'll see what I'll do. Thanks!
Lord Kixdemp
www.SulfurMidis.com
www.SulfurSoft.tk
[ftp://][http://][hotline://]tsfc.ath.cx
|
|
|
|
|
ints are generally 16-bits in DOS, but 32-bits in Windows. If you want 32-bit, use a long. If you want 16-bits, use a short - these are meant to be guaranteed between different compilers.
Ryan "Punctuality is only a virtue for those who aren't smart enough to think of good excuses for being late" John Nichol "Point Of Impact"
|
|
|
|
|
|
|
The C++ standard states that a long is 4 bytes and a short is 2 bytes. An int is defined by the size of the standard machine word for the architecture you're compiling for - 32 bits for Windows and 16-bits for DOS (unless you're using a 32-bit DOS extender such as DOS4GW).
Note that the size of a byte is not defined (other than to say it must be at least 8 bits), so a short may not actually be 16 bits, although I've never seen a situation where it is different.
Ryan "Punctuality is only a virtue for those who aren't smart enough to think of good excuses for being late" John Nichol "Point Of Impact"
|
|
|
|
|
|
Yeah, longs in .NET are 64-bits by definition.
Ryan "Punctuality is only a virtue for those who aren't smart enough to think of good excuses for being late" John Nichol "Point Of Impact"
|
|
|
|
|
|
Heya
I'm using DiLascia's CPictureCtrl in an MFC application, which works quite nicely. CPictureCtrl is essentially a wrapper around IPicture. Also, I use the gd library in my program. The dream of my sleepless nights would be to update the image displayed in the CPictureCtrl with text put into it through the gd functions. Hence, I'd need the picture to be stored in memory (which it is, inside the CPictureCtrl object) and then manipulate or replace it using gd. Any idea how to put those ends together?
Cheers
Robert
|
|
|
|
|
Hello,
Is it legal to 'delete' single elements of an array that was allocated all at once with 'new Array[Count]' ??
I want to allocate an array of stuff as in 'pArray = new Type[5];'
But I want to de-allocate each element one at a time as in:
for ( a = 0; a < Count; a ++ )
delete pArray[a];
It is giving me ASSERT failures in the C runtime, so I'm thinking that this may not be allowed.
Thanks,
Rich
|
|
|
|
|
What's your reason for wanting to do so?
|
|
|
|
|
Hi, thanks for your response. I was having a brain-lock.
Rich
|
|
|
|
|
You're allocating and deleting different things. So no, generally you can't do this.
But why would you want to do so anyway? Is your array an array of pointers? If so, make sure you do a new on each element of the array, as well as the whole array.
Ryan "Punctuality is only a virtue for those who aren't smart enough to think of good excuses for being late" John Nichol "Point Of Impact"
|
|
|
|
|
You're absolutely right. It is not an array of pointers, so when I say "delete Array[a];" I'm telling it to delete the actual instance, rather than the pointer to that instance.
So I wonder why it did not give me a compiler error?
Thanks so much,
Rich
|
|
|
|
|
Don't do that. If you need to construct/destruct individual objects, then a C-style array is the wrong thing to use.
If you could destruct individual members of an array, think what would happen when you later delete the array? The runtime will try to destruct the objects again.
--Mike--
Visual C++ MVP 
LINKS~! Ericahist | NEW!! PimpFish | CP SearchBar v3.0 | C++ Forum FAQ
|
|
|
|
|
Hi Mike,
Thank you for your response. I will have to redesign that part of the program to do it in a different way.
Rich
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
