Thanks for your feedback. Rabbit holes are so dangerous - it is good to have someone say "can't be done". If you have time, maybe you can answer another question.
In the kt macro, I am creating many tip forms. I got it hooked to a timer now so it doesn't clobber the ui usability on load (se startup). The thing is, when a form is created via _load_template(kt_formindex, _mdi, "N"); .... it steals the focus from the se main window. I try to rectify this by capturing wid and restoring it to p_window_id, and then calling _set_focus(); but that doesn't quite focus the _mdi.p_child, but if I also do _mdi.p_child._set_focus() this makes slick grab focus when you are focused on another app, which is no good because the timers take a while to complete all their creation of tip forms.
I am new to forms, and I am not sure how to persist/autoload a form (like toolbars do), or even if this would work with a borderless form, or if it would be a good idea since there are so many of them. I am guessing that if they are persisted, then I would have to make a unique form for each, opposed to 'newing' them as I do now.
Back to the cursor in window problem, I was trying to figure out how it was done by looking at the 'up()' command, as in cursor-up (up arrow) ... since that will yank the view so that the cursor is visible, but it must be happening on the exe side because I do not see any detection code in the macro.