I've run into this mildly annoying behavior with every version of FiC I've installed and finally decided to mention it. This is neither life threatening nor urgent; merely irritating.

I work with a 2 monitor setup and have my command window dockable and carefully positioned on my 2nd desktop, right above the property window, data session & document view; also dockable and these 3 docked together.

When FiC fires up VFP during the installation process, it always moves my command window. Is this something that can be suppressed? Or at least keep it where I left it before running the installer?

Hi Richard,

I have noticed that VFP changes the command window settings (to dockable on and default position) when re-starting after an abnormal termination (eg. C0005 error).

Your scenario looks different however…

When installation is complete, FICstart.exe executes that compiles the *.prgs (to avoid a 'source not available' error when you try to debug).

At the end, it starts the VFP9 IDE using a run /n command and the -c .../ab/aw/awTrial.fpw configuration file:

; VFP config file for FoxInCloud Web Application Studio shorcut

title=FoxInCloud Web Application Studio - Trial
path=..\..\..\;..\..\..\FFC;..\..\;..\;..\Graphics\;..\AT\;..\AW\
_startup=
command=do (home(1)+"tools\ab\aw\aw.app") with .t.

Maybe the _startup= directive causes the issue in your case.

Thanks for the reply, Thierry. This only happens from the installer. Starting up FiC Studio does position it where I left it.

To the best of my knowledge, VFP is reading the position of any saved windows from the foxuser resource table. When the next beta comes out, I'll pay more attention.

Well, at the end of FICstart (running after InstallShield), to let the user decide whether to run FoxInCloud studio immediately or not, we can add a messageBox() with timeout default to yes.

I just installed the new beta and here's what the installer is doing to the position of my command window:

Again, this is a minor irritation but I did promise a screenshot just to give you a visual.

One more observation. I moved my command window back where I wanted it whilst still in the FiC instance and quit. When I ran my normal VFP dev, the command window was now offset above and to the left. Definitely puzzling that the location appears to get saved back to my foxuser table with that additional offset.

we'll double check whether the way ficStart.exe starts VFP9.exe could have an impact on command window's position (no explicit action on foxuser.dbf however).

could you check whether command window's .docked status changes between your settings and the settings after ficStart?

update: of course, ficStart.exe includes a config.fpw with RESOURCE = OFF