SAPIEN Technologies

It is just like any other function. Pass an object. Design the object to have all of the properties and dependencies you need.

The correct method of handling cases like this is to pass an object that correctly maintains its properties. Once the object knows itself and can maintain the internal requirements then the function becomes trivial. Don't use old linear code methods in an object system, It will only make the coding ...

Adapter objects show up as a linked list of objects. You can query each down the list. I would get the ID and just get the base adapter object which has all adapter properties. Adapter configurations are stored sepaarately, I recommend reviewing both the WMI and the CIM models as there are many good ...

Those colors are set by the system. That means always redrawing everything in the combobox on every redraw command. . You would have to use an "OwnerDraw" combo.

Spend some time reading the dos on combo. Some just use an RtB like it is a CB.

All of those elements are separated as properties on the adapter object. Just reference them as needed.

The code for any event can be removee, edited or replaced using code any time you need to change a controls behavior.

You can also easily use an "if" to handle multiple tasks.

Strange behaviour and not what I'm used to when working with winforms without PSS in the past but I can live with it especially as I don't need to write several lines of code as a workaround any more :) I recommend reviewing the docs on WinForms, the "Control" class and each control you are having ...

What property are you calling the "ValuMemberr". Tat is only availab;e after a change takes place.

TO get teh value in the "Combo's text display box" use the "Text" property.

you are assuming that "UniqueId" is a string.

Run the "Invoke" at a prompt and inspect the returned objects.

Here is a more flexible method that is a generalization of what most of us use.