>>Well I thought of something like that as well, but I thought it wouldn't work if the app user runs issues a "clear typeahead" or its own "keyboard ... clear". So far this solution works, and I'm just happy to drop the other more complicated and potentially less stable ways of persisting this toolbar, like creating a dummy object and doing all the stuff I need from its ProjectHook object - open project survives the Clear All, but only if it's visible.
>
>Sounds like there could be a wish list item in here. Something along the lines of a less powerful CLEAR ALL or a CLEAR ALL EXCEPT or ...

The thing that needs to be fixed is docs on Clear All - first, there's no mention of projects and related objects (_vfp.projects collection) and when do they get released. Second, the fact that _screen.property will survive Clear All along with its content, but not if it's an object reference, in which case it becomes .null. - that one also needs being written.

There are good reasons for not touching Clear All in the functional sense - there are thousands of apps out there that rely on it as it is. I could only wish for it to be stronger, i.e. to kill the stuck objects as well (tablerevert() all tables with uncommitted changes, null all the object references in properties and do a general garbage collection).