Comment 3 for bug 1943387

Hi Samuel,

Xpad 5.4 is the latest released version, so that should not be the issue.
Also, this issue has not already been solved in the in development version (Xpad 5.5); I could not find anything in the Changelog.

I had a quick (and maybe insufficient) look at the source code and I cannot explain this behavior yet. Maybe I should have a more thorough look later.

But before that, I thought it could be that a new pad is 'forced' to be presented on startup by using a command-line option. These are the available options.

-------------------------------------------------------------

arthur@pb450:~$ xpad --help
Usage:
  xpad [OPTION…]

Help Options:
  -?, --help Show help options

Application Options:
  -v, --version Show version number and quit
  -N, --no-new Don't create a new pad on startup if no previous pads exist
  -n, --new Create a new pad on startup even if pads already exist
  -h, --hide Hide all pads
  -s, --show Show all pads
  -t, --toggle Toggle between show and hide all pads
  -f, --new-from-file=FILE Create a new pad with the contents of a file
  -q, --quit Close all pads

-------------------------------------------------------------

What is the exact command-line being used to start xpad on your desktop?