ede/evoke/Splash.h

57 lines
1.1 KiB
C
Raw Normal View History

2007-07-30 17:25:13 +04:00
/*
* $Id$
*
* Evoke, head honcho of everything
* Part of Equinox Desktop Environment (EDE).
* Copyright (c) 2000-2007 EDE Authors.
*
* This program is licensed under terms of the
* GNU General Public License version 2 or newer.
* See COPYING for details.
*/
#ifndef __SPLASH_H__
#define __SPLASH_H__
#include <FL/Fl_Double_Window.H>
#include <FL/Fl_Box.H>
2007-07-30 17:25:13 +04:00
#include "EvokeService.h"
class Splash : public Fl_Double_Window {
private:
2007-08-22 17:35:41 +04:00
ClientList* clist;
2007-07-30 17:25:13 +04:00
const edelib::String* bkg;
unsigned int counter;
bool no_splash;
bool dry_run;
ClientListIter clist_it;
Fl_Box* msgbox;
Fl_Box** icons;
public:
Splash(bool sp, bool dr);
~Splash();
/*
* NOTE: clients() and set_background() uses address of passed data,
* so make sure passed data does not destroys.
*/
2007-08-22 17:35:41 +04:00
void set_clients(ClientList* cl) { clist = cl; }
2007-07-30 17:25:13 +04:00
void set_background(const edelib::String* s) { bkg = s; }
const ClientList* get_clients(void) const { return clist; }
bool next_client(void);
bool next_client_nosplash(void);
void run(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
#if EDEWM_HAVE_NET_SPLASH
virtual void show(void);
#endif
2007-07-30 17:25:13 +04:00
};
#endif