Comments by David J Perez

David J Perez 2-Feb-12 12:11pm View

I tried this except for the ToolboxBitmap decoration because I don't have a bitmap and it did not work. Seems like it should. It compiled fine but the balloon does not show the Display Name or Description.

David J Perez 4-Nov-11 18:35pm View

I guess what I am referring to is the fact that there is not a single collection that has all of them. I am coming from the VB6 world where if I wanted to find any control on my form I would check Me.Controls collection and everything was in there, timers and non-timers. Looks like some kind of kludge to have a Components collection along side the Controls collection. And to have it in a section of code that I don't have control over makes it even more suspect.

Plus, right now I am unable to get Components[i].Name because the .Name property does not exist for the Timer or the Component object.

David J Perez 4-Nov-11 18:21pm View

Thanks, that's exactly what I needed. Not sure what's going on back there in xxx.Designer.cs but if I want to find non-timer controls I will use this.Controls and if I don't find it there I will try this.components.Components. Very intuitive :)

Thanks again!

David J Perez 4-Nov-11 18:08pm View

Just tried it and got the same result. I do not believe Timers are in the Controls collection because Timers do not inherit from the Controls class. But I am not sure where to get a collection of them.

David J Perez 4-Nov-11 14:59pm View

I've gone through your procedure and I did learn something about the Load event that may prove useful in the future but I don't see how it could help in this situation. This solution requires a reference to an event handler and the only way I, a newbie, know to do this is by writing code. Either I do it or I add the [attribute] and have the IDE/Compiler do it. It cannot be programmed through the Load event but I wish it could be.

David J Perez 3-Nov-11 22:01pm View

Thanks for your help!

David J Perez 3-Nov-11 22:00pm View

Your warning is a bit over my head but I am moved by your passion.

David J Perez 3-Nov-11 16:04pm View

So when I add a new control to a form instead of assigning a specific handler in my constructor I would add a new case to my generic handler. I would not have gained much.

David J Perez 3-Nov-11 15:59pm View

I can make changes to the control and add the standard event params but I would then have a switch/case tree to explicitly call the specific (as opposed to generic) handlers.

David J Perez 3-Nov-11 15:57pm View

I can make changes to the control and add the standard event params but I would have to deal with this problem again in the generic handler.

David J Perez 3-Nov-11 15:55pm View

I think this would work as you described but then I will have just moved the problem I have to the generic handler where I would then have to explicitly call each individual handler since the handlers will be wildly different.

David J Perez 8-Apr-11 13:04pm View

I tried GCHandleType.Pinned but got an exception because my structure is not "blittable". There does appear to be ways to make unblittable structures blittable but I have not run that down yet. I think GCHandleType.Weak gets me the same effect but I have not tested it.

David J Perez 8-Apr-11 12:47pm View

You're right about Buf1 and Buf2, i wanted to minimize my already too large question. I think what you propose with AllocHGlobal()will be my fallback position but I was hoping there was a more elegant solution. Thanks

Comments by David J Perez (Top 13 by date)