A
andyblum
Working with a thrid party control (Sybase DataWindow.Net). It is a
great component but I found something really wierd and need help. The
object has a field inside of it called PrimaryBuffer. This field is
null when it shouldn't be (I wont go into the details). However, when
I inspect the object inside the debugger and scroll to the Primary Data
Field it then is instantiated. Again, the act of observing the field
inside of the debugger causes its instantiation. How can I mimic this
through code so I can find a work around. I cant just instantiate it
normally because its base data type is a custom object with no
constructor. The tool is supposed to be a able to have this
instantiated and it isnt. Until I scroll through its fields in the
debugger.
I called it a quantum error because in Physics the Uncertainty
principal states that the act of observation can change its results.
Any suggestions on how I can mimic what the debugger is doing when I
scroll through the fields so I can find a work around for my code that
is blowing up.
Andy
great component but I found something really wierd and need help. The
object has a field inside of it called PrimaryBuffer. This field is
null when it shouldn't be (I wont go into the details). However, when
I inspect the object inside the debugger and scroll to the Primary Data
Field it then is instantiated. Again, the act of observing the field
inside of the debugger causes its instantiation. How can I mimic this
through code so I can find a work around. I cant just instantiate it
normally because its base data type is a custom object with no
constructor. The tool is supposed to be a able to have this
instantiated and it isnt. Until I scroll through its fields in the
debugger.
I called it a quantum error because in Physics the Uncertainty
principal states that the act of observation can change its results.
Any suggestions on how I can mimic what the debugger is doing when I
scroll through the fields so I can find a work around for my code that
is blowing up.
Andy