|
i have some text data in txt file. That thing I wnat to put on the MFC dialog window. The file get loaded when user selecte the open dialog menu clicks.
When user clicks on the line(which is a link to some other file)then one more child window will open & user can able to see the data.
That data is large so if possible then that data I want to put it on the MFC dialog window itself.
|
|
|
|
|
do we speak the same english ???  
Akshay Sankeshwari wrote: That thing I wnat to put on the MFC dialog window
WHICH dialog ? you never talked about it before, so how could we know about it ?
Akshay Sankeshwari wrote: When user clicks on the line
same remark : WHICH line ? do you have a tabular control ?
buddy, if you don't explain with much details, no one will help you ...!!!
TOXCCT >>> GEII power
[toxcct][VisualCalc 2.20][VCalc 3.0 soon...]
|
|
|
|
|
Akshay Sankeshwari wrote: When user clicks on the line(which is a link to some other file)then one more child window will open & user can able to see the data.
If the text you want to click is a properly-formed hyperlink, you can use a rich edit control as it will recognize hyperlinks.
"The greatest good you can do for another is not just to share your riches but to reveal to him his own." - Benjamin Disraeli
|
|
|
|
|
Akshay Sankeshwari wrote: That data is large so if possible then that data I want to put it on the MFC dialog window itself.
Use CStdioFile to read the Data File and Subclass the Rich Edit Control to behave url behave like clickable text
"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
|
|
|
|
|
Hi,All
Can you help me
How to read format JP2
Thanks
|
|
|
|
|
|
I have created my project in VC++ using MFCAppWizard. Can you help me to understand the Globals folder in ClassView Tab of project. Thank you.
|
|
|
|
|
I think the VC IDE scans the project files for variables and functions which are defined globally, and shows them in the Globals folder. If a variable is defined globally as static, then it will not show in the Globals folder, because that variable will be specific to the source file it is defined in.
Is it of no significant importance to you as a beginner, but you know that you can find your globally defined functions and variables there.
this is this.
|
|
|
|
|
khan++ wrote: Is it of no significant importance to you as a beginner...
I know what you are intending to say, but most beginners have a bad habit of using global variables/functions.
"The greatest good you can do for another is not just to share your riches but to reveal to him his own." - Benjamin Disraeli
|
|
|
|
|
Which PSDK API's can use to change the master volume of PC speaker & Mic
|
|
|
|
|
anilFirst wrote: Which PSDK API's can use to change the master volume of PC speaker & Mic
Please check AuxsetVolume api!
"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 !
Can someone make clear why in the beginning of most source codes programmers write following macros ?
#ifdef _DEBUG
#define new DEBUG_NEW
#undef THIS_FILE
static char THIS_FILE[] = __FILE__;
#endif
and whats the use for #pragma once macro
|
|
|
|
|
- #pragma once is the microsoft way of telling the compiler that the file is included once in a compilation unit.
it is the same as
#ifndef __MYMACRO__
#define __MYMACRO__
#endif
for the debug macros, they allow to trace the stack, knowing the file reached...
TOXCCT >>> GEII power
[toxcct][VisualCalc 2.20][VCalc 3.0 soon...]
-- modified at 5:02 Wednesday 15th February, 2006
|
|
|
|
|
toxcct wrote: #pragma once is the microsoft way of telling the compiler that the file is included once in a compilation unit.
it is the same as
what I know #ifdef #endif and pragma once functionality is different
#pragma once maintains a "include file table" for include files during compilation . But their work is same.
never say die
-- modified at 5:10 Wednesday 15th February, 2006
|
|
|
|
|
sunit5 wrote: #pragma once maintains a "include file table"
yes, but the result remains the same.
moreover, #pragma is microsoft specific, which means that it won't work for another compiler (gcc for example)...
TOXCCT >>> GEII power
[toxcct][VisualCalc 2.20][VCalc 3.0 soon...]
|
|
|
|
|
toxcct wrote: moreover, #pragma is microsoft specific, which means that it won't work for another compiler (gcc for example)...
I dont think so
never say die
|
|
|
|
|
I can only second toxcct on that, #pragma once is not standard. There may be other compilers/preprocessors that also make use of it, so it is maybe not MS specific anymore, but it is definitely not standard.
~RaGE();
|
|
|
|
|
toxcct wrote: moreover, #pragma is microsoft specific, which means that it won't work for another compiler (gcc for example)...
I think most compilers today (including gcc) support #pragma once, but it is not mandated by the Standard.
My programming blahblahblah blog. If you ever find anything useful here, please let me know to remove it.
|
|
|
|
|
sunit5 wrote: what I know #ifdef #endif and pragma once functionality is different
#pragma once maintains a "include file table" for include files during compilation . But their work is same
Almost - #pragma once prevents the entire file from being brought in by the preprocessor again. The #ifndef/#define/#endif or #if !defined/#define/#endif constructs exclude a specific range (whatever is enclosed in the #ifndef block) from being brought in again. Anything before or after the block would be brought in again.
However, the common/general use of the latter makes it pretty much the same functionality as #pragma once, but it is incorrect to assume that they both do the exact same thing.
For example, place something like DWORD Some_Value outside of the #ifndef block of a header file and #include the file twice in a CPP file somewhere and compile that CPP file. You will get an error about a redefinition. Now, add #pragma once to the header file and
try to compile the CPP file again; the error will go away.
Lastly, #pragma constructs are compiler-dependent - but that does not mean that different compilers will not use the same #pragmas for the same thing (or even different things).
Peace!
-=- James
If you think it costs a lot to do it right, just wait until you find out how much it costs to do it wrong!
Avoid driving a vehicle taller than you and remember that Professional Driver on Closed Course does not mean your Dumb Ass on a Public Road!
DeleteFXPFiles & CheckFavorites (Please rate this post!)
|
|
|
|
|
I think it is to use the special Debug version of new when you use new. This special version allocates more memory than asked for, to make room for memory leak info etc. So that when you do not de-allocate anything you got with new, you get a message in the output window about the leak.
About the THIS_FILE, I have no idea, never needed to know, too lazy to search.
As for #pragma once, it is to include the current file only once during compilation.
this is this.
|
|
|
|
|
big_denny_200 wrote: #pragma once macro
you usually find this statement in the header files ,this statement instruct the compiler to include the header file only once
big_denny_200 wrote: #ifdef _DEBUG#define new DEBUG_NEW#undef THIS_FILEstatic char THIS_FILE[] = __FILE__;#endif
this mean, if you compiling the application is debug mode define operator new as DEBUG_NEW which make debugging easy!
and for ___FILE___ macro please click this link :-
http://users.bestweb.net/~ctips/tip011.html[^]
"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
|
|
|
|
|
#ifdef _DEBUG
Checks if this a DEBUG build, if it is tell the compiler to handle everything until it encounters an #endif, if it's not a debug build it just skips this section of the source file.
#define new DEBUG_NEW
DEBUG_NEW is a special version of new which stores extra information about the memory being allocated (file name and source line the allocation was made), all we're doing here is overriding the standard version of new.
#undef THIS_FILE<br />
static char THIS_FILE[] = __FILE__;
THIS_FILE stores a copy the current source file being executed, useful for debug messages etc, eg.
char buffer[ 255 ];
sprinf( buffer, "An error occured in source file %s", THIS_FILE );
printf( buffer );
#pragma once just tells the compiler to parse a header file once per source file, else you could end up with hundreds of error messages where stuffs getting defined twice.
Gavin Taylor
w: http://www.gavspace.com
|
|
|
|
|
If i dynamically create a CString object then will this object deallocate by itself after going out of scope or should we use teh "delete" operator to deallocate it?
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
