Wed, 07 Dec 2016 19:25:58 +0300always load existing PLC program from the working directory
Andrey Skvortsov <andrej.skvortzov@gmail.com> [Wed, 07 Dec 2016 19:25:58 +0300] rev 1597
always load existing PLC program from the working directory

Wed, 07 Dec 2016 19:24:16 +0300stop PLC before unloading
Andrey Skvortsov <andrej.skvortzov@gmail.com> [Wed, 07 Dec 2016 19:24:16 +0300] rev 1596
stop PLC before unloading


This fixes segmentation fault if service was quit without stopping it.
It has happened if Beremiz service was quit using taskbar icon or by
closing Beremiz IDE (in case of autostarted local service).

In second case to trigger the bug following step has to be done:
1. Open Beremiz IDE
2. Open project, compile and connect to LOCAL:// runtime
3. Transfer and start the PLC program
4. Open other project without disconneting the PLC runtime
5. Close Beremiz IDE

Wed, 07 Dec 2016 18:32:34 +0300add internatialization support for Beremiz_service.py
Andrey Skvortsov <andrej.skvortzov@gmail.com> [Wed, 07 Dec 2016 18:32:34 +0300] rev 1595
add internatialization support for Beremiz_service.py

Wed, 07 Dec 2016 18:25:37 +0300fix issue with changing annonced Pyro service name via taskbar icon
Andrey Skvortsov <andrej.skvortzov@gmail.com> [Wed, 07 Dec 2016 18:25:37 +0300] rev 1594
fix issue with changing annonced Pyro service name via taskbar icon

Wed, 07 Dec 2016 18:23:59 +0300don't crash on trying to change IP interface for Beremiz_service using taskbar icon if IP wasn't previously
Andrey Skvortsov <andrej.skvortzov@gmail.com> [Wed, 07 Dec 2016 18:23:59 +0300] rev 1593
don't crash on trying to change IP interface for Beremiz_service using taskbar icon if IP wasn't previously


By default IP is not set (None) and service listen only on localhost interface.

Wed, 07 Dec 2016 18:15:04 +0300start/stop from taskbar icon only if PLC is stopped/started
Andrey Skvortsov <andrej.skvortzov@gmail.com> [Wed, 07 Dec 2016 18:15:04 +0300] rev 1592
start/stop from taskbar icon only if PLC is stopped/started

Wed, 07 Dec 2016 17:54:41 +0300close Pyro socket after daemon stop
Andrey Skvortsov <andrej.skvortzov@gmail.com> [Wed, 07 Dec 2016 17:54:41 +0300] rev 1591
close Pyro socket after daemon stop


without that socket port is open after daemon shutdown.
As a result if you restart daemon with new settings (service name, for example),
it can't listen on already used port and opens the next free TCP port
regardless of requested settings.