Issue 17: SingleInstance Application
Project Member Reported by nicolai....@gmail.com, Feb 4, 2012
The keyboard should only run once and more important: The keyboard should run in background, when closed and reopened, when started.
This increases performance!

It is already realized rudimentary with a socket, but has to be improved:

1. Currently, Port 4242 is used. Problems, if another app uses the port...
-> Not only check, if port is open, but also send request and wait for particular answer to validate that the keyboard is behind port
-> maybe increase port, if not free
-> if another port is used, it has to be saved anywhere. Otherwise, the keyboard could start on first port, if the other app has exited :o

2. There might be problems with firewalls?!
Feb 6, 2012
Project Member #1 nicolai....@gmail.com
1. implemented answer (only correct answer result in exiting the second application)
port is now stored in the config file, so that it can be changed
-> no plans for using more than one port

2. Windows firewall will ask... Maybe show a hind, before open socket first time?
Status: Started