RTCONTROLS UPDATE

Public WithEvents RTListBox As MSForms.ListBox Public WithEvents RTLabel As MSForms.Label MoveFocusTo method has been added to the userform that will fire soEnter or soExit, if appropriate. SetFocus method won't fire soEnter or soExit.īut a. User tabs or clicks into a different design time control, native Exit and native Enter fire.

User tabs into an RT control, native Exit event only User clicks into a RT control, both native Exit & soEnter fire User tabs into a design time control, soExit and native Enter will fire. User clicks into a design time control, no soExit event fires, the native Enter event fires for the design time control User clicks or tabs the focus into an rtControl, both soEnter and soExit will fire In clsRTControls, the MouseMove, MouseDown and KeyDown events have been coded to detect when the focus has changed. The clsRTControls object has soEnter and soExit events. This version of clsRTControl and clsRTControls adds Key Down, Press and Up events and Mouse Down, Move and Up. I think I've found a partial work-around.

RTCONTROLS UPDATE

One of the problems with custom userform objects is that they don't have Enter, Exit or Before/After Update events. You can easily test whether you have circular reference since the terminate routine of the relevant classes will not fire (since they aren't terminated) - so if you put a debug.print in, it will never print. So the resources will not be released until excel closes.įor small scale projects, this may not be much of a issue, but if you have a lot of large objects then memory usage will continue to climb for each you add and you'll eventually run out of memory. In any normal circumstances, simply letting the object go out of scope would be fine, however an object is only released when there are no further references to it - in this case there will always be a reference - VBA's garbage collector isn't advanced enough to resolve these on its own. There are a couple of ways around the issue, you could use something like weak references - so just store a pointer to the object, but it's a bit in depth, it's much easier to write a dispose method to explicitly resolve the references in order. There's a better description here: Dealing with Circular References This means that the garbage collector cannot resolve the reference hence the object resources are never released. I thought I could use a class, e.g.:īy circular reference I mean that the RTControls class holds a reference to each RTControl object, which in turn holds a reference back to the RTControls class.

Now I need a means of trapping the controls events. ObjControl.List = Sheet1.Range('A2:M3').Value 'testing only - retrieve records using SQL recordset EntireRow)Ĭall CallByName(objControl, shtFormUI.Cells(1. Set rngProperties = Intersect(shtFormUI.Range('E:X'). Public Function AddControls(ByVal objTarget As Object, ByVal strUiName As String)ĭim rngControls As Excel.Range, rngProperties As Excel.Rangeĭim rngControl As Excel.Range, rngProperty As Excel.Range

Rtcontrols