I have functionality already implemented in double click event of ListView. Now I want to add a button that would do the same, but instead of writing everything for that button click event, I just want to fire the ListView Double Click event !
My understanding is that PerformClick exists essentially so that keyboard actions like "ESC" and "Enter" can invoke a button. In general terms, I believe you are looking for more information on Events and Delegates. In other words, you can define your own events and methods with the correct signature that are "bound" to those events as handlers. Although somewhat complex, there is documentation in MSDN and the .NET Framework to understand how you can pursue this further. You might try this[^] as a starting point.
Speaking from a Tapi 2.1 perspective all you really get from Tapi is a handle to a wave device. Above that you really don't record using Tapi, that is done with the MM APIs. I am not sure about newer versions of Tapi. I think the concept is the same but the newer COM based Tapi interfaces use the concept of terminals instead of handles.
Paul Watson wrote: "At the end of the day it is what you produce that counts, not how many doctorates you have on the wall." George Carlin wrote: "Don't sweat the petty things, and don't pet the sweaty things." Jörgen Sigvardsson wrote: If the physicists find a universal theory describing the laws of universe, I'm sure the a**hole constant will be an integral part of that theory.
Look at the System.Text namespace, and in particular classes like ASCIIEncoding class.
I, for one, do not think the problem was that the band was down. I think that the problem may have been that there was a Stonehenge monument on the stage that was in danger of being crushed by a dwarf.
This is a loaded question! How good of a programmer are you? Do you truly understand the .NET Framework or just think that C# is a special language? Do you understand the C/C++ native types very well? There are so many questions that require answering that such a question cannot be answered, at least not by anyone but yourself.
Also, the Quake2 port is not written in managed code: it was merely compiled using the MS C/C++ compiler with the /clr switch turned on. This produces a mixed-mode assembly, which most often contains more native instructions than not. Therefore, not only is this assembly not verifiable it is also not cross-platform. Managed code is used where possible but the CLR cannot manage all memory as well (if at all) in a mixed-mode assembly. The article mentions something to this effect as well.
If you want to learn more about this switch and the code that's produced, what the "Enter the Programmer" segment of MSDN TV for the episode, Managed Code[^].
I have a abstract class and several decendants. These decendants hold some functions and variables witch are used by a basic user control. The point is that I need to change between the currently used decendant at runtime (by user choice). The user control updates itself during that (using events). But when I switch to a new decendant, the old one won't get deallocated ?
Witch means the more I switch to new decendants the more I consume memory ?
It would be logical if the old decendant gets freed and then a new one is initialized, but I'm not sure if that's so ?
desmond5 wrote: But when I switch to a new decendant, the old one won't get deallocated ?
Assuming that nothing else holds a reference to the old control, it will get deallocated at some point when the GC next runs. You can try forcing it to run with System.GC.Collect(), but suggested practice is to let it do it's thing.
Another thing to keep in mind. As I understand it, when your user control gets first loaded, there is some memory used as it gets JIT'd and loaded into the application. This memory can never be deallocated until the application (actually it's appdomain) shuts down.
I don't think it is a very large overhead, though. Where I work, we load hundreds of user controls dynamically without any significant leakage.