Yes, the mouse events are easy, if you draw them from a collection of objects, and iterate over that collecton backwards to see what the mouse is over, you should find it easy enough to handle mouse events and direct them to the correct object.
Christian Graus - Microsoft MVP - C++
"I am working on a project that will convert a FORTRAN code to corresponding C++ code.I am not aware of FORTRAN syntax" ( spotted in the C++/CLI forum )
I have posted before about this question and now I'm offering money for a solution
I have been using the dotNet Framework to create an UPnP Control Point application, this application makes use of the Microsoft UPNPLib.
The problem I have is when I "Invoke an Action", because the UPnP device that I am invoking the action on is building up a big response that could take a while to be recieved by my application the action keeps timing out (at around 36 seconds) can someone tell me how to extend the timeout period?
If I receive a satisfactory solution I will transfer 30GBP via PayPal to a specified account.
Freedom is the right to say that 2+2=5 if this is so everything else will follow.
No, no you have this the wrong way round. The way consultancy works is that you pay me and then i give you the answer. After all what guarantee do I have that if I posted the answer here that you would pay me? What if the answer is that there is no answer (ie. its not possible) - would you still pay me?
So, i'll do the work for £100 with pleasure (it'll only take me 10-15 minutes to confirm or deny the existance of a timeout property) and thats a better hourly rate than mine by a few times.
So let me know if you want to employ my company (I am a consultant in SE England). I don't accept paypal and I do charge VAT so I'll invoice you for the work and get started just as soon as the cheque/bank transfer clears.
Just as I thought a "Forum Tough Guy" who can talk the talk but yet he's a paraplegic.
Ive been developing sofware for around 8 years commercially and maybe 2 years as a hobbyist before that. Im far from knowing everything, but I do know how to search for solutions - its what I do on a daily basis. Its part of this job.
Just one question though, what exactly is your problem?
My problem is you. Specifically you have <50 posts at CP and you come here and dictate how you think we should conduct ourselves. You also insult us by saying that our freely given help and advice is not good enough for you - you want a level of service above everyone else.
Your behviour is akin to a child not getting their own way. You can be assured that none of your questions will be ever be answered by me.
ok try to debug(F5) your application by putting debug point where you have written the code ...... and see dropdown list contains all the values
Assuming that you know how to debug and the code that you have written is in button click event
Thanks and Regards Sandeep
If If you look at what you do not have in life, you don't have anything,
If you look at what you have in life, you have everything... "
I'm new to C#, so please bear with me if the question is obvious and/or stupid.
I have a C# (.NET Framework 2.0) application that needs to call functions in an unmanaged C/C++ DLL. The name of the DLL is unknown at compile time (so I can't use the DllImportAttribute directly). The solution I adopted uses the native LoadLibrary/GetProcAddress combination, as seen in the code snippet below.
and then used it in the constructor to store the function I'm going to call in the DLL. In order to do that, I had to use the delegate type twice: once as a parameter for GetDelegateForFunctionPointer and then again to cast the return value.
Now, this example calls a function named Run that receives no arguments and returns nothing (void), as specified by the delegate signature.
Now, my problem is that I don't know this signature at compile time. Maybe the first time it runs, the Run function will receive two strings and return a bool. Or maybe it will receive a string, two bools, an int and return a double. Or maybe something else.
What I need is to supply the return and argument types, and then create at runtime the right kind of delegate to use. I would then use this delegate created at runtime to supply the correct signature to the GetDelegateForFunctionPointer method and to correctly cast the return value. Not to mention to call my function in the DLL, of course.
If someone has any suggestions, I'd greatly appreciate the help. Code examples as well to illustrate, since I'm not at all familiar with using Reflection.Emit (I'm assuming it's going to go that way?).
Last Visit: 31-Dec-99 18:00 Last Update: 26-Sep-23 20:26