G
Guest
We use C# for our machine control application (of course C# is not doing the
real time hardware control). The C# application is mainly a GUI and domain
model proxy, which gets the machine status through hardware interface.
The domain object in C# knows how to send the command to the hardware
devices (running under realtime) and the domain object caches the status data
of the hardware it represents.
Now we are going to use data binding to connect the "Property of a GUI
control" and the "Property of the domain object". So that the domain object's
property change, for example temperature, would be automatically updated on
the GUI control property. We have hundreds of such Propreties needs to be
bind to various GUI properties. My question is what kind of overhead these
thousands of binding object would bring? Anyone has used data binding on a
large scale application?
Thx
lz
real time hardware control). The C# application is mainly a GUI and domain
model proxy, which gets the machine status through hardware interface.
The domain object in C# knows how to send the command to the hardware
devices (running under realtime) and the domain object caches the status data
of the hardware it represents.
Now we are going to use data binding to connect the "Property of a GUI
control" and the "Property of the domain object". So that the domain object's
property change, for example temperature, would be automatically updated on
the GUI control property. We have hundreds of such Propreties needs to be
bind to various GUI properties. My question is what kind of overhead these
thousands of binding object would bring? Anyone has used data binding on a
large scale application?
Thx
lz