when is uvguix.username file generated?

1) I think these are either manually created or renamed from *.uvgui(x)(.<user>) files. These are designed to represent a default screen layout that users can go back to. If no file in the form *.uvgui(x)(.<current_user>) exists beside *.uvproj(x) file, then uVision will read *.uvgui(x) file, if it exists. These GUI files are not even required, though. They are only useful for sharing or saving screen layouts.

2) New *.uvgui(x)(.<user>) file is created when new user first closes project.
The file is automatically linked with the new user. When project is closed, again, *.uvgui(x)(.<user>) is updated.

3) You can edit these files directly to change username or edit default windows, but do this when project is closed. It is usually faster for users to simply delete (.<user>) part off of *.uvgui(x)(.<user>) in Windows/File Explorer, or rename it to *.uvgui(x)(.<new_user>) to transfer debug setups between users.

1) I think these are either manually created or renamed from *.uvgui(x)(.<user>) files. These are designed to represent a default screen layout that users can go back to. If no file in the form *.uvgui(x)(.<current_user>) exists beside *.uvproj(x) file, then uVision will read *.uvgui(x) file, if it exists. These GUI files are not even required, though. They are only useful for sharing or saving screen layouts.

2) New *.uvgui(x)(.<user>) file is created when new user first closes project.
The file is automatically linked with the new user. When project is closed, again, *.uvgui(x)(.<user>) is updated.

3) You can edit these files directly to change username or edit default windows, but do this when project is closed. It is usually faster for users to simply delete (.<user>) part off of *.uvgui(x)(.<user>) in Windows/File Explorer, or rename it to *.uvgui(x)(.<new_user>) to transfer debug setups between users.