cPicture (image file manager)

[Midas]

Also, changing the font size does not stick, it remains tiny which renders the app unusable for my eyes.

Behavior confirmed when trying to enlarge the "Segoe UI" system font to 10 points; OTOH, Tahoma seemed to work (mostly) fine...

Moreover, on right-clicking the ribbon, a German context menu is shown -- selecting "Multifunktionleiste minimieren" kept the ribbon shrunk when not in use.

Also, by clicking the first drop-down menu -- which has no label and only shows two options, "Info" and "Exit" -- you can then select "Info | Command Line" and read this at the end:

-x configuration file | sets the configuration file (default is '%APPDATA%\cPicture\cPicture.config').

After moving settings and starting cPicture with this option, previous configuration was retained, although it still created an empty folder in '%APPDATA%\cPicture\' and a registry key at 'HKCU\SOFTWARE\TheCloud\' making it not really portable (but an easy one for yaP, I guess).

[Andrew Lee]

On my system (Windows 10), I was able to make it portable by simply creating an empty file called cpicture.config before running the EXE.

All settings were written to this file, including the font. It looks something like:

Code: Select all

<?xml version="1.0" encoding="utf-8" ?>
<Configuration>
 <Author>cPicture</Author>
 <Version>3.8.8</Version>
 <Settings>
  ...
  <Setting Name="SysFont" Type="bin">f2ffffff0000000000000000000000005e01000000000001030201224e00690072006d0061006c0061002000550049002000530065006d0069006c006900670068007400000000000000000000000000000000000000000000000000</Setting>
 </Settings>
</Configuration>

I tried a few fonts like "Arial", "Nirmala UI", "Open Sans" at various point sizes 12 - 16, and they all worked without issues.

Also, the AppData\Roaming\cPicture folder was not created.

[Midas]

Great. Did you check for any registry traces?

Forgot to say that I tested on Windows 10, too. (v10.0.19041.388 by ver CLI command)

[Andrew Lee]

As far as I can tell, no registry traces,

[Midas]