Well, since the contract/specification of STL's vector states that is has to use a contigious block of memory, you could write out the # of elements in one of the vectors and write out the entire block in one WriteFile(...) operation.
The address of the first element of the vector would be the start of the memory block allocated to it.
-=- James (Sonork:100.21837)
[Tip for SUV winter driving survival: "Professional Driver on Closed Course" does not mean "your Dumb Ass on a Public Road"!] [Get Delete FXP Files Now!]
I have very wierd problem with this common dialog. If i call it in my program it works fine, kind of. I get path's & filenames and everything. No problems at all, but after calling the MFC-version or the WINAPI-version of the dialog all other file IO's will fail for no reason. Just simply fails. For example fopen() fails every time after one filedialog-call. Without that call fopen works fine.
I want to Play an EMF file to a memoryDc & then display it to the screen using the BitBlt function.
Iam doing it as follows: ,but I dont see anything on screen.
I guess its because,I have to select the Emf Object into the MemoryDc.Is that So?
If yes,How could I select the Emfhandle into the memoryDc,as "SelectObject" takes only things like CBrush,Cpen,Cfont Etc...
//m_deviceContext is the destination device Context.
//meta_handle,Handle to MetaFile.
Can anyone tell me something about crystral reports. What is it and from where can i download it?
Recently a project came to me for maintenance purpose. When i try to run it, an error dialog box occured, asking me for a dll related to crystal reports. I heard this name many times before. Please tell me abt it ?
I have made an application in vc++ that uses flexgrid to show data. I have made this application on NT 2000 but when i run the setup of application on Windows XP then flexgrid is not coming in the application. Can anyone pl. tell me the reason for this.
Thanx in advance for everyone's help
I dont know how to do what you are asking for, but there is one solution though.
instead of deriving the class you can make a member variable of baseclass, then initialise the iodevice and then initialise the baseclass with the device.
I thought about the wrapper, but then I would have to reimplement in my class each public method of the class I would wrap, and then just forwarding the call to a method from my wrapper to the wrapped class. I wanted to avoid that by subclassing....