Compiled Windows Standalone App Logfile Location and Console Visibility

1. Is there a way to retrieve the location of the logfile if use the -R option programmatically rather than hardcopy so can be sure can find it for any choice of user installation location? The doc says "in application folder" but is there a way to determine that programmatically?
2. Is there any builtin functionality to clear the logfile?
3. Is there a way to programmatically display or hide the console if do not select the -e option based on, say, a debugFlag status the user can set? Would be extremely useful for debugging but avoid the annoying black console window if not hidden.

Another sidebar Q? on app building -- whassup w/ projects? AppDesigner makes a .prj file on its own, it seems, and then asks about saving changes on exit. But, then neither

appdesigner BuildBillingUtility.prj
openProject BuildBillingUtility.prj

work...the first says "...file type must be a MATLAB App (*.mlapp)."

so, ok, that leads to finding the doc for openProject but that returns

"The file "...\BuildBillingUtility.prj" is not a valid project file."

This is in both R2021b and R2022b -- was moving from the former to the latter when discovered the snafu...saved the original .mlapp file in R2021b with 'R21b' appended to base name, then reloaded the original into R2022b and did the same so as to not lose the working original if something went south in R022b.

[Rik]

I generally create my own log file (based on the AppData folder, where Matlab also generally stores data). I hardly ever work with project files (or AppDesigner), so I'm afraid I can't help you with either issue.

[dpb]

Thanks. I was running into issues on a network IT-controlled machine install with being able to create a working folder so wondered if could figure out where it put it by default that knew had write privileges. I never did locate it...I discovered that ctfroot returns some arcane path that has all the supporting runtime stuff under it, but none of the actual application files. The documentation in this area is totally incomprehensible to me, I can make no heads nor tails from it that seems to have any relationship whatsoever to what actually happens on installation.

I finally gave it up and manually add the additional data files to the "other files" and then they're also put into the install folder. As long as can rely on the user to install in the default "PROGRAMFILES" location, can find them there and then move them to a known location.

I surely wish there were a way to force the installer to pre-check the "Shortcut on Desktop" box...that gets real old real quick and unsophisticated users who don't know how to add one themselves...and don't have admin rights or confidence to reinstall themselves...