If an app version has a graphics app, the path of the graphics app is passed to GUIs in RESULT::graphics_exec_path.
This is used by the BOINC Manager (which shows a "Show Graphics" button for tasks with a graphics app) and by the BOINC screensaver (which runs graphics apps in full-screen mode by passing them the --full_screen flag). This mechanism could (and probably should) be used on Android. If a task has a graphics app, the GUI should show a "Show Graphics" button which, when pressed, launches the graphics app. -- David On 01-Oct-2013 8:01 PM, Carl Christensen wrote:
losing the transfers looks fine to me. I'd like to jump in with a new question - I'm working on an Android/BOINC app for the Quake-Catcher Network -- just monitors the built-in device accelerometer when the device is charging & "at rest". Should be very low CPU. I'm thinking of porting my OpenGL graphics over into a separate graphics app, that people can run to see the xyz plots of the accelerometer (maybe leave it on as a screen saver). I think it should be possible ie just access the shared memory from my separate graphics program and see the plots (kind of like how BOINC does it anyway, e.g. separate program). Has anybody tried this yet ie a separate graphics app? _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
_______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
