03-21-2017 02:29 AM
Previously I had not used the f1/f2 patches - not sure how I missed these. However, I have just installed the 2016 f2 patch and the controls behave in the same way. Given that the locking was not observed by Jeff, I'm uncertain what my installation/settings/configuration is unhappy with. I'll keep playing with it, but it's interesting to know it seems to only affect me - not others. I had really hoped that the CWDataSocket control would both demonstrate the problem and be more accessible than the ActiveX control I'm working with, but I guess not.
More pessimistically, this probably also means my other ActiveX control is fine - but at least I now know several work-arounds.
With regards to the other observations of Jeff (I was a bit unsure of what he means by 'Add a sub BD around the terminal of the tab container', so I probably didn't do that, but:
These were all observed (or not) using 2016 f2 32 bit, and two CWGraph ActiveX Container controls in a Tab Control.
03-21-2017 12:23 PM - edited 03-21-2017 12:29 PM
observations of Jeff (I was a bit unsure of what he means by 'Add a sub BD around the terminal of the tab container', so I probably didn't do that, but:
Sorry I was unclear, Any Structure that places a sub diagram. I put a For Loop around the terminals While loops, and disable or sequence structures of any flavor would (Hopefully) act consistently. This let me "Move" terminals with Make/Unmake Space dependant on direction and terminal placement while watching the artifacts "Live Drag" (Ctrl |Ctrl+ Alt)+RClick hold+move without toggling Live-Drag On/Off via Spacebar. [ini token to normally disable live drag defaulted]
***Another one of those "Don't ask me to explain what I just did--Here Watch this!" moments. its easier to do than explain