Firstly, I agree... 1+
In the interim, this should help the specific task you mention regarding the Open Dialog:
Code:
(vl-load-com)
(defun c:OpenHere (/ dwg)
(if (and
(setq dwg (getfiled "Select File" (getvar 'dwgprefix) "dwg" 8))
(setq dwg (findfile dwg))
)
(vla-activate
(vla-open (vla-get-documents (vlax-get-acad-object))
dwg
:vlax-false
)
)
)
(princ)
)
Now, as for a viable 'dynamic' folder, this is going to have to be done in .NET API... The reason for this, is that even when one hooks the CommandWillStart Event in LISP, the applicable registry keys (where one's favorites are stored, per profile) have already been read by native code for the OPEN Command... At least that was the behavior I observed in some limited testing with LISP.
Methinks, one could code a .NET plug-in which would hook the DocumentLockModeChanged Event, and if the DocumentLockModeChangedEventArgs.GlobalCommandName matches the small handful of desired Commands (i.e., Open, SaveAs, etc.), then the plug-in would programmatically identify, and update the appropriate registry key(s) to provide the illusion of a dynamic shortcut folder.
One implied task being that this 'link' to one or more specific shortcuts needs to be persistent... Thus stored in either an app/plug-in registry key, or what I've been leaning toward, XML within the presumed Autoloader .bundle's directory structure, which makes it a bit simpler to my mind, to store not only one dynamic folder, but a series of, and to do so per-profile. More complex than it may sound.
This has been an item on my to-do list, and now that it's a WishList item, I may just make time to complete it.
Cheers