Hmm, yeah, I can see how you may be tempted to do that. The short answer is, no, there is no such control or style. For a long winded explanation as to why not, please read on
There is a thing called CUA (Common User Access) (see https://en.wikipedia.org/wiki/IBM_Common_User_Access
) which defined a long time a go where what goes and what certain keys do in an application.
The overall goal was to make all graphical applications adhere to the same standards, so that once user was trained in one application, the knowledge gained would transfer to all other applications and thereby reduce the amount of training required. Which is why *most* windows applications look very similar and even Linux and Apple MacOS apps look somewhat familiar.
The window's caption, which is the area you want to customize, is meant to be descriptive as to the task the window represents.
So if you click on an "open..." item, the following dialog or form should be titled "Open".
The application's main window by convention contains the title of the application, centered. If an app opens documents, single or multiple, it generally either uses a prefix or a post-fix placement for the title.
My document - Very Cool App or Very Cool App - My document
This allows the user to easily comprehend which application is active and what document, if any is open. The main window's caption is also used by the Windows task bar to display information when hovering.
So in general, and that is just my private opinion, I would rather stick to the standard and not mess with that.
If you really want to do that, there is a Windows message, WM_NCPAINT (https://docs.microsoft.com/en-us/window ... wm-ncpaint
) which paints all non-client areas of a window.
It is quite a complex undertaking and I think not something you want to tackle in powershell. But you could most certainly paint the actual caption left justified rather than centered and paint additional
supplemental information wherever you like it, without disturbing the actual caption data itself.
This is however not an job for the faint of heart, (just read this https://social.msdn.microsoft.com/Forum ... evelopment
) as it involves doing what Windows normally does for you and, usually, undocumented trickery.
But if you want to do that, I wish you the best of luck