Thank you for your answer. The data is used only to restore the last program state. There is an additional export feature - so I think SQLite ore SQL CE will achieve what I want. Alex

That's good, now have you done the Happy Dance! as in the "It works, Hurah!!" :-D DTR or Data Terminal Ready some times needs to be set high on RS232 to allow the port that there is data there. Not really used that much these days I have used the DTR & CTS lines to supply power to some (smallish) circuits you can also use them as signal lines as you can control the on / off states via the true / false property (I have used the to control LED's & Relays). Good on you for finding that can I suggest the book Serial Port Complete by Jan Axelson (ISBN 978-1-931448-06-2) as a good reference (her other books are good too!, if you want to start hanging stuff out of your PC!) -=-=-=-=-=-= Also just though if the piece of hardware is a 'modern' version of an older bit of hardware it could be that the software was designed to alter DTR & CTS to send and receive data on the go and when the USB version of the hardware came about it was easier to bodge some thing like setting a pin high on the port than rewrite the software. Glenn

You're welcome :)

Thank you for your answer. At the moment, I use a formula similar to your first aproach where I get an error of up to +/- 1 pixel - it may be enough for the moment... Your second aproach is clever. Perhaps I will try it later (using an invisible bitmap filled with the index as rgba value ...). Alex

Thank you for reminding that. As far as I can see, this is already done right in the sample file. Alex

I have found an example which works as expected: http://msdn.microsoft.com/en-us/library/8c47csfz%28v=vs.90%29.aspx[^] Alex

I understand that you want the parent and type to be template parameters. So let me repeat my earlier code snippet - template<class Parent, typename Type> void AddMember(Type Parent::*Member) { return true; } Here Parent and Type are template parameters and the calling is also convenient - AddMember(&TestObject::i); Here Parent will be deduced to TestObject and Type will be deduced to int. And Member will point to i. I think this is as convenient as it can get. «_Superman_»  _I love work. It gives me something to do between weekends. _Microsoft MVP (Visual C++) Polymorphism in C

Thank you for your answer and the interesting article. However, as I mentioned, I am doing insertions within the middle of the list - so the indices change and it does not make any sense to store them in the data cell. Additionally: Your article assumes that I would have to find the right insert position and therefore the vector would be faster - but if it would have been possible to store the iterator inside the data cell, I would immediately start at the right position of my linked list. It would still be nice to have a data structure allowing access by index (not Key!) while beeing able to insert/remove elements in logarithmic time. Alex

Thank you, then it is clear! Alex

Thank you, it works.

LionAM wrote: In my case, I need the local object because it is a lock (which has to be destroyed when leaving scope). Makes sense. Just for reference, there's other ways to get the destructor called: (from Destructors and Finalizers in Visual C++[^]): Code authored in Visual C++ and compiled with /clr will run a type's destructor for the following reasons: \* If an object created using stack semantics goes out of scope. \* If an exception is thrown during the object's construction. \* If the object is a member in an object whose destructor is running. \* If you call the delete Operator (C++) on a handle (^ (Handle to Object on Managed Heap)). \* If you explicitly call the destructor. If your type is being consumed by a client authored in another language, the destructor will be called when: \* A call to Dispose. \* Calling Dispose(void) on the type. \* If the type goes out of scope in a C# using statement. Regardless, having a second reference outside the scope is a bad idea and shouldn't be necessary :) Cheers, Mark Mark Salsbery Microsoft MVP - Visual C++ :java:

Ok, nearly solved. When I override the WndProc-Method and process the WM_SYSCOMMAND(SC_MOVE) Message, I can reset the Parent-property and the window is not bounded any more. Alex

MdiClient is in the System::Windows::Forms namespace, not the System::Windows::Forms::Form namespace (which doesn't exist - System::Windows::Forms::Form is a class). Either of these should work: using namespace System::Windows::Forms; ... if (objectref->GetType() == MdiClient::typeid) or if (objectref->GetType() == System::Windows::Forms::MdiClient::typeid) Mark

Cool! As long as it meets your performance requirements and doesn't deadlock  :) Like I mentioned, there's lots of ways to do it - with "big" performance differences between the solutions. Glad you found a solution! Cheers, Mark Mark Salsbery Microsoft MVP - Visual C++ :java:

OK. Thank you. Alex

Thank you for your answers! Unfortunately this seems not to work under Visual C++ 6 (another bug?) - but it does work in VC2005 Express... But if I declare the classes as friends, it works (and I even don't need the public type cast operator). Alex

I think you should go to Project --> Settings --> C/C++ --> Category: Listing Files --> Listing file type and select Assembly with Source Code. In this case the compiler will generate ASM files and you can investigate them. I hope it helps.