2007-07-11 20:03:18 +04:00
|
|
|
/*
|
|
|
|
* $Id$
|
|
|
|
*
|
|
|
|
* Evoke, head honcho of everything
|
|
|
|
* Part of Equinox Desktop Environment (EDE).
|
A lot of changes, especially the ways how screen is repainted (in composite).
Composite will now draw only damaged regions, and their damage is (now) correctly
reported, mostly due changes in main FLTK loop.
Also there are two ways how evoke will be running: if USE_FLTK_LOOP_EMULATION
is defined (default yes), it will fully emulate FLTK loop (as done before). Oposite
way (without emulation) it will relay on FLTK message passing, but it is very unpredictable
since FLTK will sometime miss SelectionClear events (XSETTINGS relay on it), probably due
large XDamageNotify throttling. When emulation is used, there are no such problems
since all events are processed before they are routed to FLTK.
In composite is added another way of repainting (when USE_CHECK is defined), and it will
relay on Fl::add_check() function; there are some differences between this function
and timer used for screen refresh. Timer will try to refresh it every XX ms and when
there are large number of XDamageNotify reports, this will not be suitable for
movements smoothing on the screen; on other hand add_check() will call callback every
time when event is processed, which brings smooth movements. For now only timer is used
untill I finish compositing stuff.
Also composite will handle messages from it's own add_handler() since (somehow), all pending
XDamageNotify events will not be correctly reported inside EvokeService handler.
And about splash... splash will now keep it's window at the top, no matter what window is
raised. This is a small hack until I implement _NET_WM_WINDOW_TYPE_SPLASH in edewm (I don't
have to say that this hack works for all wm's I tested :P).
Sound from splash is removed; reason for this is when evoke starts childs (only when X session
was started), device descriptors will be used by childs too making sound device unusable and
marked as busy. This can be solved by using better sound library, which is story for itself...
2008-01-14 15:50:30 +03:00
|
|
|
* Copyright (c) 2007-2008 EDE Authors.
|
2007-07-11 20:03:18 +04:00
|
|
|
*
|
|
|
|
* This program is licensed under terms of the
|
|
|
|
* GNU General Public License version 2 or newer.
|
|
|
|
* See COPYING for details.
|
|
|
|
*/
|
|
|
|
|
2008-09-08 15:09:37 +04:00
|
|
|
#include <string.h>
|
|
|
|
#include <signal.h>
|
2007-07-11 20:03:18 +04:00
|
|
|
|
|
|
|
#include <edelib/Config.h>
|
|
|
|
#include <edelib/Debug.h>
|
|
|
|
#include <edelib/File.h>
|
|
|
|
|
2008-09-15 15:00:23 +04:00
|
|
|
#include <FL/Fl.H>
|
|
|
|
#include <FL/x.H>
|
2008-09-08 15:09:37 +04:00
|
|
|
|
|
|
|
#include "EvokeService.h"
|
2007-07-11 20:03:18 +04:00
|
|
|
|
|
|
|
#define FOREVER 1e20
|
|
|
|
#define CONFIG_FILE "evoke.conf"
|
|
|
|
#define DEFAULT_PID "/tmp/evoke.pid"
|
2007-07-30 17:25:13 +04:00
|
|
|
/*
|
|
|
|
* Used to assure unique instance, even if is given another
|
|
|
|
* path for pid. This option can't be modified by user.
|
|
|
|
* TODO: add lock on file so it can't be removed ?
|
|
|
|
*/
|
|
|
|
#define LOCK_FILE "/tmp/.evoke.lock"
|
2007-07-11 20:03:18 +04:00
|
|
|
|
|
|
|
#define CHECK_ARGV(argv, pshort, plong) ((strcmp(argv, pshort) == 0) || (strcmp(argv, plong) == 0))
|
|
|
|
|
2008-09-08 15:09:37 +04:00
|
|
|
static void quit_signal(int sig) {
|
2007-07-11 20:03:18 +04:00
|
|
|
EVOKE_LOG("Got quit signal %i\n", sig);
|
2007-07-30 17:25:13 +04:00
|
|
|
EvokeService::instance()->stop();
|
2007-07-11 20:03:18 +04:00
|
|
|
}
|
|
|
|
|
2008-10-08 17:22:45 +04:00
|
|
|
static int xmessage_handler(int) {
|
2008-09-08 15:09:37 +04:00
|
|
|
#ifdef USE_FLTK_LOOP_EMULATION
|
2007-09-18 18:06:09 +04:00
|
|
|
XEvent xev;
|
|
|
|
while(XEventsQueued(fl_display, QueuedAfterReading)) {
|
|
|
|
XNextEvent(fl_display, &xev);
|
|
|
|
EvokeService::instance()->handle((const XEvent*)&xev);
|
|
|
|
}
|
2008-10-08 17:22:45 +04:00
|
|
|
return 1;
|
2008-09-08 15:09:37 +04:00
|
|
|
#else
|
A lot of changes, especially the ways how screen is repainted (in composite).
Composite will now draw only damaged regions, and their damage is (now) correctly
reported, mostly due changes in main FLTK loop.
Also there are two ways how evoke will be running: if USE_FLTK_LOOP_EMULATION
is defined (default yes), it will fully emulate FLTK loop (as done before). Oposite
way (without emulation) it will relay on FLTK message passing, but it is very unpredictable
since FLTK will sometime miss SelectionClear events (XSETTINGS relay on it), probably due
large XDamageNotify throttling. When emulation is used, there are no such problems
since all events are processed before they are routed to FLTK.
In composite is added another way of repainting (when USE_CHECK is defined), and it will
relay on Fl::add_check() function; there are some differences between this function
and timer used for screen refresh. Timer will try to refresh it every XX ms and when
there are large number of XDamageNotify reports, this will not be suitable for
movements smoothing on the screen; on other hand add_check() will call callback every
time when event is processed, which brings smooth movements. For now only timer is used
untill I finish compositing stuff.
Also composite will handle messages from it's own add_handler() since (somehow), all pending
XDamageNotify events will not be correctly reported inside EvokeService handler.
And about splash... splash will now keep it's window at the top, no matter what window is
raised. This is a small hack until I implement _NET_WM_WINDOW_TYPE_SPLASH in edewm (I don't
have to say that this hack works for all wm's I tested :P).
Sound from splash is removed; reason for this is when evoke starts childs (only when X session
was started), device descriptors will be used by childs too making sound device unusable and
marked as busy. This can be solved by using better sound library, which is story for itself...
2008-01-14 15:50:30 +03:00
|
|
|
return EvokeService::instance()->handle(fl_xevent);
|
2008-09-08 15:09:37 +04:00
|
|
|
#endif
|
A lot of changes, especially the ways how screen is repainted (in composite).
Composite will now draw only damaged regions, and their damage is (now) correctly
reported, mostly due changes in main FLTK loop.
Also there are two ways how evoke will be running: if USE_FLTK_LOOP_EMULATION
is defined (default yes), it will fully emulate FLTK loop (as done before). Oposite
way (without emulation) it will relay on FLTK message passing, but it is very unpredictable
since FLTK will sometime miss SelectionClear events (XSETTINGS relay on it), probably due
large XDamageNotify throttling. When emulation is used, there are no such problems
since all events are processed before they are routed to FLTK.
In composite is added another way of repainting (when USE_CHECK is defined), and it will
relay on Fl::add_check() function; there are some differences between this function
and timer used for screen refresh. Timer will try to refresh it every XX ms and when
there are large number of XDamageNotify reports, this will not be suitable for
movements smoothing on the screen; on other hand add_check() will call callback every
time when event is processed, which brings smooth movements. For now only timer is used
untill I finish compositing stuff.
Also composite will handle messages from it's own add_handler() since (somehow), all pending
XDamageNotify events will not be correctly reported inside EvokeService handler.
And about splash... splash will now keep it's window at the top, no matter what window is
raised. This is a small hack until I implement _NET_WM_WINDOW_TYPE_SPLASH in edewm (I don't
have to say that this hack works for all wm's I tested :P).
Sound from splash is removed; reason for this is when evoke starts childs (only when X session
was started), device descriptors will be used by childs too making sound device unusable and
marked as busy. This can be solved by using better sound library, which is story for itself...
2008-01-14 15:50:30 +03:00
|
|
|
}
|
|
|
|
|
2008-10-08 17:22:45 +04:00
|
|
|
#ifdef USE_FLTK_LOOP_EMULATION
|
|
|
|
static void xmessage_handler_fd(int, void*) {
|
|
|
|
xmessage_handler(0);
|
|
|
|
}
|
|
|
|
|
2008-09-08 15:09:37 +04:00
|
|
|
static int composite_handler(int ev) {
|
A lot of changes, especially the ways how screen is repainted (in composite).
Composite will now draw only damaged regions, and their damage is (now) correctly
reported, mostly due changes in main FLTK loop.
Also there are two ways how evoke will be running: if USE_FLTK_LOOP_EMULATION
is defined (default yes), it will fully emulate FLTK loop (as done before). Oposite
way (without emulation) it will relay on FLTK message passing, but it is very unpredictable
since FLTK will sometime miss SelectionClear events (XSETTINGS relay on it), probably due
large XDamageNotify throttling. When emulation is used, there are no such problems
since all events are processed before they are routed to FLTK.
In composite is added another way of repainting (when USE_CHECK is defined), and it will
relay on Fl::add_check() function; there are some differences between this function
and timer used for screen refresh. Timer will try to refresh it every XX ms and when
there are large number of XDamageNotify reports, this will not be suitable for
movements smoothing on the screen; on other hand add_check() will call callback every
time when event is processed, which brings smooth movements. For now only timer is used
untill I finish compositing stuff.
Also composite will handle messages from it's own add_handler() since (somehow), all pending
XDamageNotify events will not be correctly reported inside EvokeService handler.
And about splash... splash will now keep it's window at the top, no matter what window is
raised. This is a small hack until I implement _NET_WM_WINDOW_TYPE_SPLASH in edewm (I don't
have to say that this hack works for all wm's I tested :P).
Sound from splash is removed; reason for this is when evoke starts childs (only when X session
was started), device descriptors will be used by childs too making sound device unusable and
marked as busy. This can be solved by using better sound library, which is story for itself...
2008-01-14 15:50:30 +03:00
|
|
|
return EvokeService::instance()->composite_handle(fl_xevent);
|
|
|
|
}
|
2008-10-08 17:22:45 +04:00
|
|
|
#endif
|
A lot of changes, especially the ways how screen is repainted (in composite).
Composite will now draw only damaged regions, and their damage is (now) correctly
reported, mostly due changes in main FLTK loop.
Also there are two ways how evoke will be running: if USE_FLTK_LOOP_EMULATION
is defined (default yes), it will fully emulate FLTK loop (as done before). Oposite
way (without emulation) it will relay on FLTK message passing, but it is very unpredictable
since FLTK will sometime miss SelectionClear events (XSETTINGS relay on it), probably due
large XDamageNotify throttling. When emulation is used, there are no such problems
since all events are processed before they are routed to FLTK.
In composite is added another way of repainting (when USE_CHECK is defined), and it will
relay on Fl::add_check() function; there are some differences between this function
and timer used for screen refresh. Timer will try to refresh it every XX ms and when
there are large number of XDamageNotify reports, this will not be suitable for
movements smoothing on the screen; on other hand add_check() will call callback every
time when event is processed, which brings smooth movements. For now only timer is used
untill I finish compositing stuff.
Also composite will handle messages from it's own add_handler() since (somehow), all pending
XDamageNotify events will not be correctly reported inside EvokeService handler.
And about splash... splash will now keep it's window at the top, no matter what window is
raised. This is a small hack until I implement _NET_WM_WINDOW_TYPE_SPLASH in edewm (I don't
have to say that this hack works for all wm's I tested :P).
Sound from splash is removed; reason for this is when evoke starts childs (only when X session
was started), device descriptors will be used by childs too making sound device unusable and
marked as busy. This can be solved by using better sound library, which is story for itself...
2008-01-14 15:50:30 +03:00
|
|
|
|
2008-09-08 15:09:37 +04:00
|
|
|
static const char* next_param(int curr, char** argv, int argc) {
|
2007-07-11 20:03:18 +04:00
|
|
|
int j = curr + 1;
|
|
|
|
if(j >= argc)
|
|
|
|
return NULL;
|
|
|
|
if(argv[j][0] == '-')
|
|
|
|
return NULL;
|
|
|
|
return argv[j];
|
|
|
|
}
|
|
|
|
|
2008-10-08 17:22:45 +04:00
|
|
|
static void help(void) {
|
A lot of changes, especially the ways how screen is repainted (in composite).
Composite will now draw only damaged regions, and their damage is (now) correctly
reported, mostly due changes in main FLTK loop.
Also there are two ways how evoke will be running: if USE_FLTK_LOOP_EMULATION
is defined (default yes), it will fully emulate FLTK loop (as done before). Oposite
way (without emulation) it will relay on FLTK message passing, but it is very unpredictable
since FLTK will sometime miss SelectionClear events (XSETTINGS relay on it), probably due
large XDamageNotify throttling. When emulation is used, there are no such problems
since all events are processed before they are routed to FLTK.
In composite is added another way of repainting (when USE_CHECK is defined), and it will
relay on Fl::add_check() function; there are some differences between this function
and timer used for screen refresh. Timer will try to refresh it every XX ms and when
there are large number of XDamageNotify reports, this will not be suitable for
movements smoothing on the screen; on other hand add_check() will call callback every
time when event is processed, which brings smooth movements. For now only timer is used
untill I finish compositing stuff.
Also composite will handle messages from it's own add_handler() since (somehow), all pending
XDamageNotify events will not be correctly reported inside EvokeService handler.
And about splash... splash will now keep it's window at the top, no matter what window is
raised. This is a small hack until I implement _NET_WM_WINDOW_TYPE_SPLASH in edewm (I don't
have to say that this hack works for all wm's I tested :P).
Sound from splash is removed; reason for this is when evoke starts childs (only when X session
was started), device descriptors will be used by childs too making sound device unusable and
marked as busy. This can be solved by using better sound library, which is story for itself...
2008-01-14 15:50:30 +03:00
|
|
|
puts("Usage: evoke [OPTIONS]");
|
2007-07-11 20:03:18 +04:00
|
|
|
puts("EDE startup manager responsible for starting, quitting and tracking");
|
|
|
|
puts("various pieces of desktop environment and external programs.");
|
|
|
|
puts("...and to popup a nice window when something crashes...\n");
|
|
|
|
puts("Options:");
|
|
|
|
puts(" -h, --help this help");
|
|
|
|
puts(" -s, --startup run in starup mode");
|
2007-07-30 17:25:13 +04:00
|
|
|
puts(" -n, --no-splash do not show splash screen in starup mode");
|
|
|
|
puts(" -d, --dry-run run in starup mode, but don't execute anything");
|
2007-09-11 18:06:44 +04:00
|
|
|
puts(" -a, --autostart read autostart directory and run all items");
|
|
|
|
puts(" -u, --autostart-safe read autostart directory and display dialog what will be run");
|
2007-07-11 20:03:18 +04:00
|
|
|
puts(" -c, --config [FILE] use FILE as config file");
|
|
|
|
puts(" -p, --pid [FILE] use FILE to store PID number");
|
2007-07-30 17:25:13 +04:00
|
|
|
puts(" -l, --log [FILE] log traffic to FILE (FILE can be stdout/stderr for console output)\n");
|
2007-07-11 20:03:18 +04:00
|
|
|
}
|
|
|
|
|
|
|
|
int main(int argc, char** argv) {
|
|
|
|
const char* config_file = NULL;
|
|
|
|
const char* pid_file = NULL;
|
|
|
|
const char* log_file = NULL;
|
|
|
|
|
2007-09-11 18:06:44 +04:00
|
|
|
bool do_startup = 0;
|
|
|
|
bool do_dryrun = 0;
|
|
|
|
bool no_splash = 0;
|
|
|
|
bool do_autostart = 0;
|
|
|
|
bool do_autostart_safe = 0;
|
2007-07-11 20:03:18 +04:00
|
|
|
|
|
|
|
if(argc > 1) {
|
|
|
|
const char* a;
|
|
|
|
for(int i = 1; i < argc; i++) {
|
|
|
|
a = argv[i];
|
|
|
|
if(CHECK_ARGV(a, "-h", "--help")) {
|
|
|
|
help();
|
|
|
|
return 0;
|
|
|
|
} else if(CHECK_ARGV(a, "-c", "--config")) {
|
|
|
|
config_file = next_param(i, argv, argc);
|
|
|
|
if(!config_file) {
|
|
|
|
puts("Missing configuration filename");
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
i++;
|
|
|
|
} else if(CHECK_ARGV(a, "-p", "--pid")) {
|
|
|
|
pid_file = next_param(i, argv, argc);
|
|
|
|
if(!pid_file) {
|
|
|
|
puts("Missing pid filename");
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
i++;
|
|
|
|
} else if(CHECK_ARGV(a, "-l", "--log")) {
|
|
|
|
log_file = next_param(i, argv, argc);
|
|
|
|
if(!log_file) {
|
|
|
|
puts("Missing log filename");
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
i++;
|
|
|
|
}
|
|
|
|
else if(CHECK_ARGV(a, "-s", "--startup"))
|
2007-07-30 17:25:13 +04:00
|
|
|
do_startup = 1;
|
|
|
|
else if(CHECK_ARGV(a, "-d", "--dry-run"))
|
|
|
|
do_dryrun = 1;
|
|
|
|
else if(CHECK_ARGV(a, "-n", "--no-splash"))
|
|
|
|
no_splash = 1;
|
2007-07-31 19:37:12 +04:00
|
|
|
else if(CHECK_ARGV(a, "-a", "--autostart"))
|
|
|
|
do_autostart = 1;
|
2007-09-11 18:06:44 +04:00
|
|
|
else if(CHECK_ARGV(a, "-u", "--autostart-safe"))
|
|
|
|
do_autostart_safe = 1;
|
2007-07-11 20:03:18 +04:00
|
|
|
else {
|
A lot of changes, especially the ways how screen is repainted (in composite).
Composite will now draw only damaged regions, and their damage is (now) correctly
reported, mostly due changes in main FLTK loop.
Also there are two ways how evoke will be running: if USE_FLTK_LOOP_EMULATION
is defined (default yes), it will fully emulate FLTK loop (as done before). Oposite
way (without emulation) it will relay on FLTK message passing, but it is very unpredictable
since FLTK will sometime miss SelectionClear events (XSETTINGS relay on it), probably due
large XDamageNotify throttling. When emulation is used, there are no such problems
since all events are processed before they are routed to FLTK.
In composite is added another way of repainting (when USE_CHECK is defined), and it will
relay on Fl::add_check() function; there are some differences between this function
and timer used for screen refresh. Timer will try to refresh it every XX ms and when
there are large number of XDamageNotify reports, this will not be suitable for
movements smoothing on the screen; on other hand add_check() will call callback every
time when event is processed, which brings smooth movements. For now only timer is used
untill I finish compositing stuff.
Also composite will handle messages from it's own add_handler() since (somehow), all pending
XDamageNotify events will not be correctly reported inside EvokeService handler.
And about splash... splash will now keep it's window at the top, no matter what window is
raised. This is a small hack until I implement _NET_WM_WINDOW_TYPE_SPLASH in edewm (I don't
have to say that this hack works for all wm's I tested :P).
Sound from splash is removed; reason for this is when evoke starts childs (only when X session
was started), device descriptors will be used by childs too making sound device unusable and
marked as busy. This can be solved by using better sound library, which is story for itself...
2008-01-14 15:50:30 +03:00
|
|
|
printf("Unknown parameter '%s'. Run 'evoke -h' for options\n", a);
|
2007-07-11 20:03:18 +04:00
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2007-07-25 18:54:21 +04:00
|
|
|
// make sure X11 is running before rest of code is called
|
2007-07-11 20:03:18 +04:00
|
|
|
fl_open_display();
|
|
|
|
|
A lot of changes, especially the ways how screen is repainted (in composite).
Composite will now draw only damaged regions, and their damage is (now) correctly
reported, mostly due changes in main FLTK loop.
Also there are two ways how evoke will be running: if USE_FLTK_LOOP_EMULATION
is defined (default yes), it will fully emulate FLTK loop (as done before). Oposite
way (without emulation) it will relay on FLTK message passing, but it is very unpredictable
since FLTK will sometime miss SelectionClear events (XSETTINGS relay on it), probably due
large XDamageNotify throttling. When emulation is used, there are no such problems
since all events are processed before they are routed to FLTK.
In composite is added another way of repainting (when USE_CHECK is defined), and it will
relay on Fl::add_check() function; there are some differences between this function
and timer used for screen refresh. Timer will try to refresh it every XX ms and when
there are large number of XDamageNotify reports, this will not be suitable for
movements smoothing on the screen; on other hand add_check() will call callback every
time when event is processed, which brings smooth movements. For now only timer is used
untill I finish compositing stuff.
Also composite will handle messages from it's own add_handler() since (somehow), all pending
XDamageNotify events will not be correctly reported inside EvokeService handler.
And about splash... splash will now keep it's window at the top, no matter what window is
raised. This is a small hack until I implement _NET_WM_WINDOW_TYPE_SPLASH in edewm (I don't
have to say that this hack works for all wm's I tested :P).
Sound from splash is removed; reason for this is when evoke starts childs (only when X session
was started), device descriptors will be used by childs too making sound device unusable and
marked as busy. This can be solved by using better sound library, which is story for itself...
2008-01-14 15:50:30 +03:00
|
|
|
// initialize main service object
|
2007-07-11 20:03:18 +04:00
|
|
|
EvokeService* service = EvokeService::instance();
|
|
|
|
|
|
|
|
if(!service->setup_logging(log_file)) {
|
|
|
|
printf("Can't open %s for logging. Please choose some writeable place\n", log_file);
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
2007-09-24 15:47:42 +04:00
|
|
|
if(!service->setup_channels()) {
|
|
|
|
printf("Can't setup internal channels\n");
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
A lot of changes, especially the ways how screen is repainted (in composite).
Composite will now draw only damaged regions, and their damage is (now) correctly
reported, mostly due changes in main FLTK loop.
Also there are two ways how evoke will be running: if USE_FLTK_LOOP_EMULATION
is defined (default yes), it will fully emulate FLTK loop (as done before). Oposite
way (without emulation) it will relay on FLTK message passing, but it is very unpredictable
since FLTK will sometime miss SelectionClear events (XSETTINGS relay on it), probably due
large XDamageNotify throttling. When emulation is used, there are no such problems
since all events are processed before they are routed to FLTK.
In composite is added another way of repainting (when USE_CHECK is defined), and it will
relay on Fl::add_check() function; there are some differences between this function
and timer used for screen refresh. Timer will try to refresh it every XX ms and when
there are large number of XDamageNotify reports, this will not be suitable for
movements smoothing on the screen; on other hand add_check() will call callback every
time when event is processed, which brings smooth movements. For now only timer is used
untill I finish compositing stuff.
Also composite will handle messages from it's own add_handler() since (somehow), all pending
XDamageNotify events will not be correctly reported inside EvokeService handler.
And about splash... splash will now keep it's window at the top, no matter what window is
raised. This is a small hack until I implement _NET_WM_WINDOW_TYPE_SPLASH in edewm (I don't
have to say that this hack works for all wm's I tested :P).
Sound from splash is removed; reason for this is when evoke starts childs (only when X session
was started), device descriptors will be used by childs too making sound device unusable and
marked as busy. This can be solved by using better sound library, which is story for itself...
2008-01-14 15:50:30 +03:00
|
|
|
EVOKE_LOG("= evoke started =\n");
|
2007-07-11 20:03:18 +04:00
|
|
|
|
|
|
|
if(!pid_file)
|
|
|
|
pid_file = DEFAULT_PID;
|
|
|
|
|
2007-07-30 17:25:13 +04:00
|
|
|
if(!service->setup_pid(pid_file, LOCK_FILE)) {
|
A lot of changes, especially the ways how screen is repainted (in composite).
Composite will now draw only damaged regions, and their damage is (now) correctly
reported, mostly due changes in main FLTK loop.
Also there are two ways how evoke will be running: if USE_FLTK_LOOP_EMULATION
is defined (default yes), it will fully emulate FLTK loop (as done before). Oposite
way (without emulation) it will relay on FLTK message passing, but it is very unpredictable
since FLTK will sometime miss SelectionClear events (XSETTINGS relay on it), probably due
large XDamageNotify throttling. When emulation is used, there are no such problems
since all events are processed before they are routed to FLTK.
In composite is added another way of repainting (when USE_CHECK is defined), and it will
relay on Fl::add_check() function; there are some differences between this function
and timer used for screen refresh. Timer will try to refresh it every XX ms and when
there are large number of XDamageNotify reports, this will not be suitable for
movements smoothing on the screen; on other hand add_check() will call callback every
time when event is processed, which brings smooth movements. For now only timer is used
untill I finish compositing stuff.
Also composite will handle messages from it's own add_handler() since (somehow), all pending
XDamageNotify events will not be correctly reported inside EvokeService handler.
And about splash... splash will now keep it's window at the top, no matter what window is
raised. This is a small hack until I implement _NET_WM_WINDOW_TYPE_SPLASH in edewm (I don't
have to say that this hack works for all wm's I tested :P).
Sound from splash is removed; reason for this is when evoke starts childs (only when X session
was started), device descriptors will be used by childs too making sound device unusable and
marked as busy. This can be solved by using better sound library, which is story for itself...
2008-01-14 15:50:30 +03:00
|
|
|
printf("Either another evoke instance is running or can't create pid file. Please correct this\n");
|
2007-12-03 16:39:22 +03:00
|
|
|
printf("Note: if program abnormaly crashed before, just remove '%s' and start it again\n", LOCK_FILE);
|
A lot of changes, especially the ways how screen is repainted (in composite).
Composite will now draw only damaged regions, and their damage is (now) correctly
reported, mostly due changes in main FLTK loop.
Also there are two ways how evoke will be running: if USE_FLTK_LOOP_EMULATION
is defined (default yes), it will fully emulate FLTK loop (as done before). Oposite
way (without emulation) it will relay on FLTK message passing, but it is very unpredictable
since FLTK will sometime miss SelectionClear events (XSETTINGS relay on it), probably due
large XDamageNotify throttling. When emulation is used, there are no such problems
since all events are processed before they are routed to FLTK.
In composite is added another way of repainting (when USE_CHECK is defined), and it will
relay on Fl::add_check() function; there are some differences between this function
and timer used for screen refresh. Timer will try to refresh it every XX ms and when
there are large number of XDamageNotify reports, this will not be suitable for
movements smoothing on the screen; on other hand add_check() will call callback every
time when event is processed, which brings smooth movements. For now only timer is used
untill I finish compositing stuff.
Also composite will handle messages from it's own add_handler() since (somehow), all pending
XDamageNotify events will not be correctly reported inside EvokeService handler.
And about splash... splash will now keep it's window at the top, no matter what window is
raised. This is a small hack until I implement _NET_WM_WINDOW_TYPE_SPLASH in edewm (I don't
have to say that this hack works for all wm's I tested :P).
Sound from splash is removed; reason for this is when evoke starts childs (only when X session
was started), device descriptors will be used by childs too making sound device unusable and
marked as busy. This can be solved by using better sound library, which is story for itself...
2008-01-14 15:50:30 +03:00
|
|
|
printf("= evoke abrupted shutdown =\n");
|
2007-07-11 20:03:18 +04:00
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
|
|
|
if(!config_file)
|
|
|
|
config_file = CONFIG_FILE; // TODO: XDG paths
|
|
|
|
|
2007-07-30 17:25:13 +04:00
|
|
|
if(do_startup) {
|
|
|
|
if(!service->init_splash(config_file, no_splash, do_dryrun)) {
|
|
|
|
EVOKE_LOG("Unable to read correctly %s. Please check it is correct config file\n", config_file);
|
A lot of changes, especially the ways how screen is repainted (in composite).
Composite will now draw only damaged regions, and their damage is (now) correctly
reported, mostly due changes in main FLTK loop.
Also there are two ways how evoke will be running: if USE_FLTK_LOOP_EMULATION
is defined (default yes), it will fully emulate FLTK loop (as done before). Oposite
way (without emulation) it will relay on FLTK message passing, but it is very unpredictable
since FLTK will sometime miss SelectionClear events (XSETTINGS relay on it), probably due
large XDamageNotify throttling. When emulation is used, there are no such problems
since all events are processed before they are routed to FLTK.
In composite is added another way of repainting (when USE_CHECK is defined), and it will
relay on Fl::add_check() function; there are some differences between this function
and timer used for screen refresh. Timer will try to refresh it every XX ms and when
there are large number of XDamageNotify reports, this will not be suitable for
movements smoothing on the screen; on other hand add_check() will call callback every
time when event is processed, which brings smooth movements. For now only timer is used
untill I finish compositing stuff.
Also composite will handle messages from it's own add_handler() since (somehow), all pending
XDamageNotify events will not be correctly reported inside EvokeService handler.
And about splash... splash will now keep it's window at the top, no matter what window is
raised. This is a small hack until I implement _NET_WM_WINDOW_TYPE_SPLASH in edewm (I don't
have to say that this hack works for all wm's I tested :P).
Sound from splash is removed; reason for this is when evoke starts childs (only when X session
was started), device descriptors will be used by childs too making sound device unusable and
marked as busy. This can be solved by using better sound library, which is story for itself...
2008-01-14 15:50:30 +03:00
|
|
|
EVOKE_LOG("= evoke abrupted shutdown =\n");
|
2007-07-30 17:25:13 +04:00
|
|
|
return 1;
|
|
|
|
}
|
2007-07-11 20:03:18 +04:00
|
|
|
}
|
|
|
|
|
|
|
|
service->setup_atoms(fl_display);
|
2007-09-18 18:06:09 +04:00
|
|
|
service->init_xsettings_manager();
|
A lot of changes, especially the ways how screen is repainted (in composite).
Composite will now draw only damaged regions, and their damage is (now) correctly
reported, mostly due changes in main FLTK loop.
Also there are two ways how evoke will be running: if USE_FLTK_LOOP_EMULATION
is defined (default yes), it will fully emulate FLTK loop (as done before). Oposite
way (without emulation) it will relay on FLTK message passing, but it is very unpredictable
since FLTK will sometime miss SelectionClear events (XSETTINGS relay on it), probably due
large XDamageNotify throttling. When emulation is used, there are no such problems
since all events are processed before they are routed to FLTK.
In composite is added another way of repainting (when USE_CHECK is defined), and it will
relay on Fl::add_check() function; there are some differences between this function
and timer used for screen refresh. Timer will try to refresh it every XX ms and when
there are large number of XDamageNotify reports, this will not be suitable for
movements smoothing on the screen; on other hand add_check() will call callback every
time when event is processed, which brings smooth movements. For now only timer is used
untill I finish compositing stuff.
Also composite will handle messages from it's own add_handler() since (somehow), all pending
XDamageNotify events will not be correctly reported inside EvokeService handler.
And about splash... splash will now keep it's window at the top, no matter what window is
raised. This is a small hack until I implement _NET_WM_WINDOW_TYPE_SPLASH in edewm (I don't
have to say that this hack works for all wm's I tested :P).
Sound from splash is removed; reason for this is when evoke starts childs (only when X session
was started), device descriptors will be used by childs too making sound device unusable and
marked as busy. This can be solved by using better sound library, which is story for itself...
2008-01-14 15:50:30 +03:00
|
|
|
|
|
|
|
/*
|
|
|
|
* Run autostart code after XSETTINGS manager since some Gtk apps (mozilla) will eats a lot
|
|
|
|
* of cpu during runtime settings changes
|
|
|
|
*/
|
|
|
|
if(do_autostart || do_autostart_safe)
|
|
|
|
service->init_autostart(do_autostart_safe);
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Let composite manager be run the latest. Running autostart after it will not deliver
|
|
|
|
* X events to possible shown autostart window, and I'm not sure why. Probably due event
|
|
|
|
* throttle from XDamage ?
|
|
|
|
*/
|
2007-12-28 13:58:56 +03:00
|
|
|
service->init_composite();
|
2007-07-11 20:03:18 +04:00
|
|
|
|
2007-09-17 14:36:24 +04:00
|
|
|
signal(SIGINT, quit_signal);
|
2007-07-11 20:03:18 +04:00
|
|
|
signal(SIGTERM, quit_signal);
|
|
|
|
signal(SIGKILL, quit_signal);
|
2007-09-17 14:36:24 +04:00
|
|
|
signal(SIGQUIT, quit_signal);
|
|
|
|
|
|
|
|
#ifdef USE_SIGHUP
|
|
|
|
/*
|
|
|
|
* This is mostly used when we get request to shutdown session and close/kill all windows.
|
|
|
|
* If evoke is started from gui console (xterm, rxvt), closing that window we will get
|
|
|
|
* SIGHUP since terminal will disconnect all controlling processes. On other hand, if evoke
|
|
|
|
* is started as session carrier (eg. run from xinitrc), this is not needed.
|
|
|
|
*/
|
|
|
|
signal(SIGHUP, quit_signal);
|
|
|
|
#endif
|
2007-07-11 20:03:18 +04:00
|
|
|
|
2007-12-28 13:58:56 +03:00
|
|
|
#if 0
|
2007-07-30 17:25:13 +04:00
|
|
|
XSelectInput(fl_display, RootWindow(fl_display, fl_screen), PropertyChangeMask | SubstructureNotifyMask | ClientMessage);
|
2007-12-28 13:58:56 +03:00
|
|
|
#endif
|
|
|
|
// composite engine included too
|
|
|
|
XSelectInput(fl_display, RootWindow(fl_display, fl_screen),
|
|
|
|
SubstructureNotifyMask | ExposureMask | StructureNotifyMask | PropertyChangeMask | ClientMessage);
|
2007-07-11 20:03:18 +04:00
|
|
|
|
|
|
|
/*
|
|
|
|
* Register event listener and run in infinite loop. Loop will be
|
|
|
|
* interrupted from one of the received signals.
|
|
|
|
*
|
A lot of changes, especially the ways how screen is repainted (in composite).
Composite will now draw only damaged regions, and their damage is (now) correctly
reported, mostly due changes in main FLTK loop.
Also there are two ways how evoke will be running: if USE_FLTK_LOOP_EMULATION
is defined (default yes), it will fully emulate FLTK loop (as done before). Oposite
way (without emulation) it will relay on FLTK message passing, but it is very unpredictable
since FLTK will sometime miss SelectionClear events (XSETTINGS relay on it), probably due
large XDamageNotify throttling. When emulation is used, there are no such problems
since all events are processed before they are routed to FLTK.
In composite is added another way of repainting (when USE_CHECK is defined), and it will
relay on Fl::add_check() function; there are some differences between this function
and timer used for screen refresh. Timer will try to refresh it every XX ms and when
there are large number of XDamageNotify reports, this will not be suitable for
movements smoothing on the screen; on other hand add_check() will call callback every
time when event is processed, which brings smooth movements. For now only timer is used
untill I finish compositing stuff.
Also composite will handle messages from it's own add_handler() since (somehow), all pending
XDamageNotify events will not be correctly reported inside EvokeService handler.
And about splash... splash will now keep it's window at the top, no matter what window is
raised. This is a small hack until I implement _NET_WM_WINDOW_TYPE_SPLASH in edewm (I don't
have to say that this hack works for all wm's I tested :P).
Sound from splash is removed; reason for this is when evoke starts childs (only when X session
was started), device descriptors will be used by childs too making sound device unusable and
marked as busy. This can be solved by using better sound library, which is story for itself...
2008-01-14 15:50:30 +03:00
|
|
|
* I choose to use fltk for this since wait() will nicely poll events
|
2007-07-11 20:03:18 +04:00
|
|
|
* and pass expecting ones to xmessage_handler(). Other (non-fltk) solution would
|
|
|
|
* be to manually pool events via select() and that code could be very messy.
|
|
|
|
* So stick with the simplicity :)
|
2007-09-18 18:06:09 +04:00
|
|
|
*
|
A lot of changes, especially the ways how screen is repainted (in composite).
Composite will now draw only damaged regions, and their damage is (now) correctly
reported, mostly due changes in main FLTK loop.
Also there are two ways how evoke will be running: if USE_FLTK_LOOP_EMULATION
is defined (default yes), it will fully emulate FLTK loop (as done before). Oposite
way (without emulation) it will relay on FLTK message passing, but it is very unpredictable
since FLTK will sometime miss SelectionClear events (XSETTINGS relay on it), probably due
large XDamageNotify throttling. When emulation is used, there are no such problems
since all events are processed before they are routed to FLTK.
In composite is added another way of repainting (when USE_CHECK is defined), and it will
relay on Fl::add_check() function; there are some differences between this function
and timer used for screen refresh. Timer will try to refresh it every XX ms and when
there are large number of XDamageNotify reports, this will not be suitable for
movements smoothing on the screen; on other hand add_check() will call callback every
time when event is processed, which brings smooth movements. For now only timer is used
untill I finish compositing stuff.
Also composite will handle messages from it's own add_handler() since (somehow), all pending
XDamageNotify events will not be correctly reported inside EvokeService handler.
And about splash... splash will now keep it's window at the top, no matter what window is
raised. This is a small hack until I implement _NET_WM_WINDOW_TYPE_SPLASH in edewm (I don't
have to say that this hack works for all wm's I tested :P).
Sound from splash is removed; reason for this is when evoke starts childs (only when X session
was started), device descriptors will be used by childs too making sound device unusable and
marked as busy. This can be solved by using better sound library, which is story for itself...
2008-01-14 15:50:30 +03:00
|
|
|
* Also note that '1' in add_fd (when USE_FLTK_LOOP_EMULATION is defined) parameter
|
|
|
|
* means POLLIN, and for the details see Fl_x.cxx
|
|
|
|
*
|
|
|
|
* Let me explaint what these USE_FLTK_LOOP_EMULATION parts means. It was introduced
|
|
|
|
* since FLTK eats up SelectionClear event and so other parts (evoke specific atoms, splash etc.)
|
|
|
|
* could be used and tested. FLTK does not have event handler that could be registered
|
|
|
|
* _before_ it process events, but only add_handler() which will be called _after_ FLTK process
|
|
|
|
* all events and where will be reported ones that FLTK does not understainds or for those
|
|
|
|
* windows it already don't know.
|
2007-07-11 20:03:18 +04:00
|
|
|
*/
|
A lot of changes, especially the ways how screen is repainted (in composite).
Composite will now draw only damaged regions, and their damage is (now) correctly
reported, mostly due changes in main FLTK loop.
Also there are two ways how evoke will be running: if USE_FLTK_LOOP_EMULATION
is defined (default yes), it will fully emulate FLTK loop (as done before). Oposite
way (without emulation) it will relay on FLTK message passing, but it is very unpredictable
since FLTK will sometime miss SelectionClear events (XSETTINGS relay on it), probably due
large XDamageNotify throttling. When emulation is used, there are no such problems
since all events are processed before they are routed to FLTK.
In composite is added another way of repainting (when USE_CHECK is defined), and it will
relay on Fl::add_check() function; there are some differences between this function
and timer used for screen refresh. Timer will try to refresh it every XX ms and when
there are large number of XDamageNotify reports, this will not be suitable for
movements smoothing on the screen; on other hand add_check() will call callback every
time when event is processed, which brings smooth movements. For now only timer is used
untill I finish compositing stuff.
Also composite will handle messages from it's own add_handler() since (somehow), all pending
XDamageNotify events will not be correctly reported inside EvokeService handler.
And about splash... splash will now keep it's window at the top, no matter what window is
raised. This is a small hack until I implement _NET_WM_WINDOW_TYPE_SPLASH in edewm (I don't
have to say that this hack works for all wm's I tested :P).
Sound from splash is removed; reason for this is when evoke starts childs (only when X session
was started), device descriptors will be used by childs too making sound device unusable and
marked as busy. This can be solved by using better sound library, which is story for itself...
2008-01-14 15:50:30 +03:00
|
|
|
#ifdef USE_FLTK_LOOP_EMULATION
|
2008-10-08 17:22:45 +04:00
|
|
|
Fl::add_fd(ConnectionNumber(fl_display), 1, xmessage_handler_fd);
|
A lot of changes, especially the ways how screen is repainted (in composite).
Composite will now draw only damaged regions, and their damage is (now) correctly
reported, mostly due changes in main FLTK loop.
Also there are two ways how evoke will be running: if USE_FLTK_LOOP_EMULATION
is defined (default yes), it will fully emulate FLTK loop (as done before). Oposite
way (without emulation) it will relay on FLTK message passing, but it is very unpredictable
since FLTK will sometime miss SelectionClear events (XSETTINGS relay on it), probably due
large XDamageNotify throttling. When emulation is used, there are no such problems
since all events are processed before they are routed to FLTK.
In composite is added another way of repainting (when USE_CHECK is defined), and it will
relay on Fl::add_check() function; there are some differences between this function
and timer used for screen refresh. Timer will try to refresh it every XX ms and when
there are large number of XDamageNotify reports, this will not be suitable for
movements smoothing on the screen; on other hand add_check() will call callback every
time when event is processed, which brings smooth movements. For now only timer is used
untill I finish compositing stuff.
Also composite will handle messages from it's own add_handler() since (somehow), all pending
XDamageNotify events will not be correctly reported inside EvokeService handler.
And about splash... splash will now keep it's window at the top, no matter what window is
raised. This is a small hack until I implement _NET_WM_WINDOW_TYPE_SPLASH in edewm (I don't
have to say that this hack works for all wm's I tested :P).
Sound from splash is removed; reason for this is when evoke starts childs (only when X session
was started), device descriptors will be used by childs too making sound device unusable and
marked as busy. This can be solved by using better sound library, which is story for itself...
2008-01-14 15:50:30 +03:00
|
|
|
Fl::add_handler(composite_handler);
|
|
|
|
#else
|
|
|
|
/*
|
|
|
|
* NOTE: composite_handler() is not needed since it will be included
|
2008-09-08 15:09:37 +04:00
|
|
|
* within xmessage_handler() call
|
A lot of changes, especially the ways how screen is repainted (in composite).
Composite will now draw only damaged regions, and their damage is (now) correctly
reported, mostly due changes in main FLTK loop.
Also there are two ways how evoke will be running: if USE_FLTK_LOOP_EMULATION
is defined (default yes), it will fully emulate FLTK loop (as done before). Oposite
way (without emulation) it will relay on FLTK message passing, but it is very unpredictable
since FLTK will sometime miss SelectionClear events (XSETTINGS relay on it), probably due
large XDamageNotify throttling. When emulation is used, there are no such problems
since all events are processed before they are routed to FLTK.
In composite is added another way of repainting (when USE_CHECK is defined), and it will
relay on Fl::add_check() function; there are some differences between this function
and timer used for screen refresh. Timer will try to refresh it every XX ms and when
there are large number of XDamageNotify reports, this will not be suitable for
movements smoothing on the screen; on other hand add_check() will call callback every
time when event is processed, which brings smooth movements. For now only timer is used
untill I finish compositing stuff.
Also composite will handle messages from it's own add_handler() since (somehow), all pending
XDamageNotify events will not be correctly reported inside EvokeService handler.
And about splash... splash will now keep it's window at the top, no matter what window is
raised. This is a small hack until I implement _NET_WM_WINDOW_TYPE_SPLASH in edewm (I don't
have to say that this hack works for all wm's I tested :P).
Sound from splash is removed; reason for this is when evoke starts childs (only when X session
was started), device descriptors will be used by childs too making sound device unusable and
marked as busy. This can be solved by using better sound library, which is story for itself...
2008-01-14 15:50:30 +03:00
|
|
|
*/
|
2008-09-08 15:09:37 +04:00
|
|
|
Fl::add_handler(xmessage_handler);
|
A lot of changes, especially the ways how screen is repainted (in composite).
Composite will now draw only damaged regions, and their damage is (now) correctly
reported, mostly due changes in main FLTK loop.
Also there are two ways how evoke will be running: if USE_FLTK_LOOP_EMULATION
is defined (default yes), it will fully emulate FLTK loop (as done before). Oposite
way (without emulation) it will relay on FLTK message passing, but it is very unpredictable
since FLTK will sometime miss SelectionClear events (XSETTINGS relay on it), probably due
large XDamageNotify throttling. When emulation is used, there are no such problems
since all events are processed before they are routed to FLTK.
In composite is added another way of repainting (when USE_CHECK is defined), and it will
relay on Fl::add_check() function; there are some differences between this function
and timer used for screen refresh. Timer will try to refresh it every XX ms and when
there are large number of XDamageNotify reports, this will not be suitable for
movements smoothing on the screen; on other hand add_check() will call callback every
time when event is processed, which brings smooth movements. For now only timer is used
untill I finish compositing stuff.
Also composite will handle messages from it's own add_handler() since (somehow), all pending
XDamageNotify events will not be correctly reported inside EvokeService handler.
And about splash... splash will now keep it's window at the top, no matter what window is
raised. This is a small hack until I implement _NET_WM_WINDOW_TYPE_SPLASH in edewm (I don't
have to say that this hack works for all wm's I tested :P).
Sound from splash is removed; reason for this is when evoke starts childs (only when X session
was started), device descriptors will be used by childs too making sound device unusable and
marked as busy. This can be solved by using better sound library, which is story for itself...
2008-01-14 15:50:30 +03:00
|
|
|
#endif
|
|
|
|
|
|
|
|
service->start();
|
|
|
|
|
|
|
|
while(service->running()) {
|
|
|
|
#ifdef USE_FLTK_LOOP_EMULATION
|
|
|
|
/*
|
|
|
|
* Seems that when XQLength() is not used, damage events will not be correctly
|
|
|
|
* send to xmessage_handler() and composite will wrongly draw the screen.
|
|
|
|
*/
|
|
|
|
if(XQLength(fl_display)) {
|
2008-10-08 17:22:45 +04:00
|
|
|
xmessage_handler(0);
|
A lot of changes, especially the ways how screen is repainted (in composite).
Composite will now draw only damaged regions, and their damage is (now) correctly
reported, mostly due changes in main FLTK loop.
Also there are two ways how evoke will be running: if USE_FLTK_LOOP_EMULATION
is defined (default yes), it will fully emulate FLTK loop (as done before). Oposite
way (without emulation) it will relay on FLTK message passing, but it is very unpredictable
since FLTK will sometime miss SelectionClear events (XSETTINGS relay on it), probably due
large XDamageNotify throttling. When emulation is used, there are no such problems
since all events are processed before they are routed to FLTK.
In composite is added another way of repainting (when USE_CHECK is defined), and it will
relay on Fl::add_check() function; there are some differences between this function
and timer used for screen refresh. Timer will try to refresh it every XX ms and when
there are large number of XDamageNotify reports, this will not be suitable for
movements smoothing on the screen; on other hand add_check() will call callback every
time when event is processed, which brings smooth movements. For now only timer is used
untill I finish compositing stuff.
Also composite will handle messages from it's own add_handler() since (somehow), all pending
XDamageNotify events will not be correctly reported inside EvokeService handler.
And about splash... splash will now keep it's window at the top, no matter what window is
raised. This is a small hack until I implement _NET_WM_WINDOW_TYPE_SPLASH in edewm (I don't
have to say that this hack works for all wm's I tested :P).
Sound from splash is removed; reason for this is when evoke starts childs (only when X session
was started), device descriptors will be used by childs too making sound device unusable and
marked as busy. This can be solved by using better sound library, which is story for itself...
2008-01-14 15:50:30 +03:00
|
|
|
continue;
|
|
|
|
}
|
|
|
|
#else
|
|
|
|
/*
|
|
|
|
* FLTK will not report SelectionClear needed for XSETTINGS manager
|
|
|
|
* so we must catch it first before FLTK discards it (if we can :P)
|
|
|
|
* This can be missed greatly due a large number of XDamage events
|
|
|
|
* and using this method is not quite safe.
|
|
|
|
*/
|
|
|
|
if(fl_xevent && fl_xevent->type == SelectionClear)
|
|
|
|
service->handle(fl_xevent);
|
|
|
|
#endif
|
2007-09-18 18:06:09 +04:00
|
|
|
|
2007-07-11 20:03:18 +04:00
|
|
|
Fl::wait(FOREVER);
|
|
|
|
|
A lot of changes, especially the ways how screen is repainted (in composite).
Composite will now draw only damaged regions, and their damage is (now) correctly
reported, mostly due changes in main FLTK loop.
Also there are two ways how evoke will be running: if USE_FLTK_LOOP_EMULATION
is defined (default yes), it will fully emulate FLTK loop (as done before). Oposite
way (without emulation) it will relay on FLTK message passing, but it is very unpredictable
since FLTK will sometime miss SelectionClear events (XSETTINGS relay on it), probably due
large XDamageNotify throttling. When emulation is used, there are no such problems
since all events are processed before they are routed to FLTK.
In composite is added another way of repainting (when USE_CHECK is defined), and it will
relay on Fl::add_check() function; there are some differences between this function
and timer used for screen refresh. Timer will try to refresh it every XX ms and when
there are large number of XDamageNotify reports, this will not be suitable for
movements smoothing on the screen; on other hand add_check() will call callback every
time when event is processed, which brings smooth movements. For now only timer is used
untill I finish compositing stuff.
Also composite will handle messages from it's own add_handler() since (somehow), all pending
XDamageNotify events will not be correctly reported inside EvokeService handler.
And about splash... splash will now keep it's window at the top, no matter what window is
raised. This is a small hack until I implement _NET_WM_WINDOW_TYPE_SPLASH in edewm (I don't
have to say that this hack works for all wm's I tested :P).
Sound from splash is removed; reason for this is when evoke starts childs (only when X session
was started), device descriptors will be used by childs too making sound device unusable and
marked as busy. This can be solved by using better sound library, which is story for itself...
2008-01-14 15:50:30 +03:00
|
|
|
#ifndef USE_FLTK_LOOP_EMULATION
|
|
|
|
if(fl_xevent && fl_xevent->type == SelectionClear)
|
|
|
|
service->handle(fl_xevent);
|
|
|
|
#endif
|
|
|
|
}
|
|
|
|
|
|
|
|
EVOKE_LOG("= evoke nice shutdown =\n");
|
2007-07-11 20:03:18 +04:00
|
|
|
return 0;
|
|
|
|
}
|