Boinc-client Version 6.x.x, Обсуждение работы шестой версии клиента Налаштування

[(_KoDAk_)]

ПОЛНАЯ история изменений версий BOINC с датами выхода релизов

Change Log для 6.11.хх

BOINC (6 - 6.10.58) Versions Change Log

BOINC 6.7/6.8/GR6.8 Change Log

Все версии боинка для закачки

ВСЕ ВЕРСИИ С 5-й по 6-ю <- РЕКОМЕНДУЕТСЯ КАЧАТЬ ОТСЮДА.

все версии, включая самые последние девелоперские!

официальный форум разработчиков (зарегистрироваться)

[(_KoDAk_)]

This version is to be released later today or this week as a replacement for 6.4.5
Change Log 6.4.6:

- client: add <no_gpus> config option
- WINSETUP: Fix the problem introduced where Enable Application execution wasn't working.
- MGR: Don't convert strings to ANSI juts to have to reconvert them back to Unicode. Fix several help link issues.Fixes #826
- WINSCR: Fix the BOINC text displayed is the screensaver control panel applet
- WINSCR: Get rid of the 'Up to 5 second wait' for the data thread to terminate. Force terminate the thread and clean up the graphics app in a clean-up routine. Forcing the user to wait when they return to the system isn't a good idea.
- WINSCR: Fix screensaver issue where the screensaver locks up when the graphics application deadlocks for one reason or another.

Create two new threads:

1. Monitor system for keyboard and mouse events.
2. Shuffle window z-order positions if needed.

The keyboard/mouse event monitor is isolated from either the core client getting stuck in a loop and not returning the results of an RPC or the window shuffling code which can get stuck if the graphics application dead locks.

The window shuffle code is isolated due to the BroadcastSystemMessage?() API using something akin to SendMessage?() which waits for a return value from the target windows winproc. If a graphics application deadlocks for one reason or another it'll cause the thread to stall. This isn't terminal and so we just wait for the next time the data thread chooses a new application and terminates the old one which will cause the thread to resume.

This should resolve all outstanding issues with the screensaver not exiting when the mouse or keyboard is used.