|
sampath-padamatinti wrote: I need to convert outlook contact information into a text file or a rtf format.
Use the File Export function of Outlook.
|
|
|
|
|
Thanx for Replay,
Hey I want to perform this operation using MAPI programming. Any samples If you know please tell me.
sampath-padamatinti
|
|
|
|
|
sampath-padamatinti wrote: Hey I want to perform this operation using MAPI programming. Any samples If you know please tell me.
Hi,
See Accessing the address book data using MAPI[^]
“Follow your bliss.” – Joseph Campbell
|
|
|
|
|
Hello sirs ,
How to convert 24 bit bmp to 16 bit bmp ... i tried many workouts but its all fake to convert 16 bit bmp as my search ..
So please give me your valuable suggestion
Thanks
|
|
|
|
|
raju_Code wrote: i tried many workouts
What have you tried? Why is it all fake? Have you read the documentation [^]?
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.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke
[My articles]
|
|
|
|
|
CPallini wrote :
What have you tried? Why is it all fake?
Thanks for your replay Sir ...i tried means ...i build some sample application from codeproject but its not creating 16 bit bmp ....
this is my workout
actually this application do's Converting DCM 2 BMP ... i can able to convert 8 and 24 bit ..its creating perfectly ..using DCMTK package but 16 bit bmp its having problem ....
this is my code snippet
bool CxImageDCM::LoadDCM(const TCHAR* filename)
{
DcmFileFormat *dfile = new DcmFileFormat();
OFCondition cond = dfile->loadFile(filename, EXS_Unknown,
EGL_withoutGL,DCM_MaxReadLength,OFFalse);
if (cond.bad()) {
AfxMessageBox(cond.text());
}
E_TransferSyntax xfer = dfile->getDataset()->getOriginalXfer();
DicomImage *di = new DicomImage(dfile, xfer,
CIF_AcrNemaCompatibility ,
0, 1);
if (di->getStatus() != EIS_Normal)
AfxMessageBox(DicomImage::getString(di->getStatus()));
di->writeBMP("D:\\Esm.bmp",8,0);
return CxImage::Load("D:\\from_dicom.bmp",CXIMAGE_FORMAT_BMP);
}
Please give me your valuable suggestion ....sir i am waiting for your replay ..
Thanks
|
|
|
|
|
Well, you may obtain a 16 bit bitmap from a 24 bit one: it's a quite lenghty coding task, but it isn't too difficult (starting point: CreateBitmap documentation [^]). If you ahve the option of using GDI+ then have a look at Bitmap::ConvertFormat method [^].
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.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke
[My articles]
|
|
|
|
|
hi all i have an application in which i have to wipe/clean all the deleted files and folder from disk. please tell me how it will possible.
thanks
|
|
|
|
|
Maybe you can write a program to put bytes of random values to the unused space of the disk, for example, by creating a large file that fills the whole disk space. That will erase all deleted files, I believe.
|
|
|
|
|
Or before you delete the file write garbage in it...
Rozis
|
|
|
|
|
That works as long as he erases the files he wants to delete (using his application.) If the program wants to erase all the deleted files and folders (they might be deleted by other programs) it still needs a way to get rid of all the traces of those files on the disk.
|
|
|
|
|
Hi
After debuging a MFC Application ,then closing it produce the following
message in the output window .
Dbug
Loaded 'ntdll.dll', no matching symbolic information found.
Loaded 'C:\WINDOWS\system32\kernel32.dll', no matching symbolic information found.
"
"
"
Loaded 'C:\WINDOWS\system32\gdi32.dll', no matching symbolic information found.
Loaded 'C:\WINDOWS\system32\user32.dll', no matching symbolic information found.
Loaded 'C:\WINDOWS\system32\comctl32.dll', no matching symbolic information found.
Loaded 'C:\WINDOWS\system32\advapi32.dll', no matching symbolic information found.
Loaded 'C:\WINDOWS\system32\rpcrt4.dll', no matching symbolic information found.
What does it mean? Thanks in advance 
|
|
|
|
|
|
It simply shows u log that which of the dlls it used for running ur MFC application.
|
|
|
|
|
can we make class cant be derived at all? if yes how to make it. please let meknow?
Nice talking to you.  If you judge people, you have no time to love them. -- Mother Teresa
|
|
|
|
|
class foo sealed
{
};
use the 'sealed' keyword.
|
|
|
|
|
theCPkid wrote: use the 'sealed' keyword.
The ISO standard C++ has no such keyword.
“Follow your bliss.” – Joseph Campbell
|
|
|
|
|
okay.. Thanks for the information.
Visual studio compiler supports this keyword [^] and above all,if a person happens to use VS, "it works" without "any additional implications".
Making the c'tor private will certainly stop the class from being inherited but it will also force the person to provide 'other' way of creating the class object.
I think OP wanted to stop inheriting not instantiation. And my suggestion only helped him do what he wanted - nothing more, nothing less.
|
|
|
|
|
theCPkid wrote: Visual studio compiler supports this keyword [^] and above all,if a person happens to use VS, "it works" without "any additional implications".
That's plainly wrong. If you scroll down to the bottom of the page you linked to, you will see this:
Requirements (Read as "Additional implications"):
Compiler option: /clr
Which means that it is not a C++ program! It is a C++/CLI program, that targets the .NET framework.
theCPkid wrote: Making the c'tor private will certainly stop the class from being inherited but it will also force the person to provide 'other' way of creating the class object.
Of course yes. But so what? That's the only way as far as C++ (the real C++) is concerned.
theCPkid wrote: I think OP wanted to stop inheriting not instantiation. And my suggestion only helped him do what he wanted - nothing more, nothing less.
Your suggestion was just wrong here. It is a correct answer if the query was posted on a managed c++ forum.
“Follow your bliss.” – Joseph Campbell
|
|
|
|
|
Rajesh R Subramanian wrote: Which means that it is not a C++ program! It is a C++/CLI program, that targets the .NET framework.
Now certainly, it's david vs big-fat-goliath(that's you) given my insufficient knowledge about managed or unmanaged code but man, if you do not scroll to the end of page, you will see this line
"sealed is also valid when compiling for native targets (without /clr)"
I have nothing more to say on this and whatever you say after that is correct but can you confirm this by using 'sealed' keyword in native unmanaged application on your system. I feel it's working on my PC.
|
|
|
|
|
theCPkid wrote: Now certainly, it's david vs big-fat-goliath(that's you) given my insufficient knowledge about managed or unmanaged code
Certainly no! I'm not trying to talk you down or something like that. I'm merely stating the facts that I can pull off my head. My idea of visiting the forums and discussing with people is to teach them some, and learn some from them back.
theCPkid wrote: "sealed is also valid when compiling for native targets (without /clr)"
Probably MS has done something with *their* compiler to support this feature (read as added feature specific to their compiler, or an extension, because of which you won't be able to have the same code successfully compiled with another c++ compiler). It doesn't work just right on my machine (you're probably using some latest version of VS and that compiler support for understanding this keyword).
I only have 2003 installed here on this PC and it doesn't just work right. I will be able to derive classes from a class that has been declared 'sealed'.
theCPkid wrote: I feel it's working on my PC.
Now, what does that mean? Something like:
class c1 sealed{}; class c2:public c1{}; gives a compiler error? If yes, then I'm almost certain that it becomes Microsoft C++ compiler (insert version) specific. Because it doesn't even work right with the previous versions! Not to mention sealed is NOT a C++ keyword.
“Follow your bliss.” – Joseph Campbell
|
|
|
|
|
class A sealed
{
};
class B: public A
{
};
error C3246: 'B' : cannot inherit from 'A' as it has been declared as 'sealed'
I use VS 2008.
Rajesh R Subramanian wrote: I only have 2003 installed here on this PC and it doesn't just work right. I will be able to derive classes from a class that has been declared 'sealed'.
Do you mean your compiler recognizes sealed keyword, allows compilation etc and still do not stop you from inheriting? hmmm.. may be you should tweak around a bit to find out how 'sealed' is being interpreted by your VS compiler.
In the msdn link I mentioned before, it is written sealed is valid even if /clr is not mentioned.
So, my suggestion is not entirely wrong. It works in at least one case. 
|
|
|
|
|
I do a rebuild all and it barfed all over. It doesn't even seem to know what does 'sealed' mean. Won't even compile. Which would be the case with every other c++ compiler.
(the previous build had ignored the changes I made to the code - happens every now and then).
theCPkid wrote: So, my suggestion is not entirely wrong. It works in at least one case. Laugh
Right.
“Follow your bliss.” – Joseph Campbell
|
|
|
|
|
Rajesh R Subramanian wrote: It doesn't even seem to know what does 'sealed' mean.
I just tried this with VC++ Express and it compiled just as theCPkid states, even though the MSDN document states that you need the /clr option - which I certainly did not use. Is this a bug or a new feature I wonder 
|
|
|
|
|
No it isn't a bug. It is some sort of an extension to their compiler.
Even though there is nothing called "sealed" in the c++ language, Microsoft seem to have added the ability to their native c++ compiler to understand and support this keyword (the idea must have come from .NET). It looks like only VS 2005 or above will support this keyword.
This cannot even be said to be "Microsoft Specific" (note that the documentation avoids using this term too), because it is restrictive to some versions of their compilers. Unfortunately if you would like to write portable code, using it is a very bad idea, because any other standard c++ compiler won't even know what sealed means. You will have to rewrite your code such that your class is not inheritable (and that will require you to change the whole class code, and the code that is using the class).
And if you want to write a class that is not inheritable, and if you use this feature, then the code is NOT c++. Because it won't even compile in any standards conformant c++ compiler.
“Follow your bliss.” – Joseph Campbell
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
