window messages. In effect, let Windows do the default thing. This removes
the hacks which kept the screensaver running with old versions of
Microsoft's keyboard/mouse driver software installed.
clientscr/
screensaver_win.cpp, .h
svn path=/trunk/boinc/; revision=25607
problem attempt to provoke Windows into redrawing the primary
display. It turns out that the screensaver image is a ghost
image, so create a blank top-most window and close it after
the graphics application has been terminated.
clientscr/
screensaver_win.cpp, .h
svn path=/trunk/boinc/; revision=24013
Klein a pattern started to emerge. At the end of the log files the last
message logged was 0x12 which translates into WM_QUIT. The latest
documentation on WM_QUIT states it should never show up in the message
loop to begin with.
The docs now say that WM_QUIT should not be sent to the message loop by
way of PostMessage. We have been doing things this way for over 5 years.
For all I know, this could have been carried over from the original screen
saver sample application.
Change the shutdown logic so that only the primary curtain window can call
PostQuitMessage() and all other curtain windows just exit when they receive
a WM_DESTROY message.
I'm not sure what causes this to be a problem on some machines and not
others. But preliminary results from Jacob are encouraging.
clientscr/
screensaver_win.cpp, .h
svn path=/trunk/boinc/; revision=23294
thread. Preserve the handle to take more drastic actions should
that not work.
clientscr/
mac_saver_module.cpp, .h
screensaver.cpp
screensaver_win.cpp, .h
svn path=/trunk/boinc/; revision=23233
- MGR: If connected to the localhost, don't display the computer name
in the window title.
- MGR: Change the exit menu item text to be a little more specific about
what is being shutdown. Use the same scheme as the exit text in the
status bar so that it'll automatically be localized.
- SCR: Remove some old Win9x code.
clientgui/
AdvancedFrame.cpp
BOINCTaskBar.cpp
clientscr/
screensaver_win.cpp, .h
svn path=/trunk/boinc/; revision=22402
chipsets exhibit an interesting situation. It appears as though
in certain conditions a single monitor machine actually reports
itself as having three monitors. Normally the monitor that
contains the primary window (coord 0,0) is on monitor 0, but on
these machines coord 0,0 is actually on monitor 2. This led to the
screensaver not properly exiting when keyboard and/or mouse activity
was detected. Now when we detect that keyboard and/or mouse activity
has happened we send the WM_INTERRUPTSAVER event to all windows
on all monitors.
clientscr/
screensaver_win.cpp, .h
svn path=/trunk/boinc/; revision=17728
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.
clientscr/
boinc_ss.rc
screensaver.cpp
screensaver_win.cpp, .h
svn path=/trunk/boinc/; revision=17336
at startup from within the BOINC Manager itself.
- MGR: Add a command line argument which specifies that the Manager was
launched by the OS.
- SCR: Remove the code that checks for the BOINC Manager shortcuts.
clientgui/
AdvancedFrame.cpp
BOINCGUIApp.cpp, .h
DlgOptions.cpp, .h
boinc_ss.h
boinc_ss.rc
screensaver_win.cpp, .h
svn path=/trunk/boinc/; revision=16406
activity and the notification window check. They should not depend
on whether or not the graphics window has been displayed or not.
clientscr/
screensaver.cpp
screensaver_win.cpp, .h
svn path=/trunk/boinc/; revision=15840
running when no graphics are available. Increased the size to the box
displaying the message to accommodate larger image sizes. Add code to
center images if less then the allowed max size of 450x166
- Screen Saver (merge from 5.10): If graphics are not available, then rotate
through the currently running results (it will change every 10 seconds)
for display so that all are presented
- Manager (merge from 5.10): During an auto-attach initiated by a project_init.xml file, Mozilla
based browsers are checking cookies in the domain (ex: worldcommunitygrid.org)
for a project while IE cookies were only being checked for the full project
dns (www.worldcommunitygrid.org). IE has been changed so that it will also
check the domain. This mechanism is generic and can be used by any project or
account manager.
- Manager (merge from 5.10): During an auto-attach initiated by a project_init.xml file,
the code to check for the Setup cookie within an IE browser would fail and cause
the attach to project dialogue to close with no warning in the event that there
is a cookie set for the project but there is not a Setup cookie.
- WCG files: Updated image, icon and installer files for WCG
svn path=/trunk/boinc/; revision=13755
Rom Walton