*
* Permission is hereby granted, free of charge, to any person obtaining a
* copy of this software and associated documentation files (the "Software"),
* to deal in the Software without restriction, including without limitation
* the rights to use, copy, modify, merge, publish, distribute, sublicense,
* Software is furnished to do so, subject to the following conditions:
*
* The above copyright notice and this permission notice (including the next
* paragraph) shall be included in all copies or substantial portions of the
* Software.
*
* THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
* IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
* FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
* THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
* LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
* FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
* DEALINGS IN THE SOFTWARE.
*/
/*
**
** win_update.c
**
** Routines of the update phase for windows.
*/
#include <assert.h>
#ifdef SERVER_DGA
#endif /* SERVER_DGA */
#include "dga_incls.h"
#include "pix_grab.h"
#include "mbufsetstr.h"
#include "rtn_grab.h"
/*
** Note: for the sake of simplicity, we always report the following
** types of changes whenever an alias or mbufset composition change
** occurs. We could try to optimize the change reporting and only
** report an attribute change if we know that the attribute has definitely
** changed since the last lock. But this requires a lot of comparison
** between the current and previous lock subjects and the decision
** tree gets quite large. This method of "over reporting" may result
** in some redundant change reports. If we want to do this type of optimization
** in the future, we still can. But for now we keep it simple.
**
** These are the window changes that are automatically reported whenever
** an alias or mbufset composition change occurs.
**
** site
** clip
** curs
** bstore
*/
/*
** ENTRY ROUTINE FOR WINDOW UPDATE PHASE
*/
int
{
/*
** 1. The first thing we do in the update phase is to synchronize
** the client structure. When all pertinent client change
** counters match the server, we are synchronized. The
** reason we must do this in a loop is that some of the
** synchronizations require us to temporarily unlock and
** relock. While the drawable is unlocked, it can undergo
** more changes, so we may need to start the synchronization
** process over.
*/
/* Determine sequence counts for state reported to client */
/* start accumulating changes */
dgawin->changeMask = 0;
do {
/* first, see if the window shared info is still valid */
if (dgai_mbsmemb_syncZombie(dgawin)) {
break;
}
/* next, we must check the multibuffer state.
This may alter the effective lock subject, whose type the
other synchronization checks depend on */
}
/* synchronize with current changes to attributes of
the effective lock subject -- depends on the type
of the current lock subject */
} else {
/* should never happen */
assert(0);
}
/* Note: whether we need to sync again depends on the type too */
/* Check if the devinfo has changed */
/*
** 2. The foregoing synchronization step has determined whether
** any attribute changes have occurred. We must now determine
** if there are any derivative changes to report.
**
** Currently, the only derivative changes for a window or viewable
** multibuffer are those in common with all mbufset members.
*/
/*
** 3. Next, we must report changes through notification functions,
** if possible.
*/
/* report any changes that we can through notification */
/*
** 4. Lastly, indicate that we are fully synchronized and get out.
*/
/* the dgawin client structure is now fully synchronized with the
shared info */
/*
** 5. If this is an overlay window, then we need to tell the
** server that we may have modified the opaque shape.
*/
*dgawin->s_ovlshapevalid_p = 0;
/* if there are still any changes that were not notified through notification
functions, DGA_DRAW_MODIF will return nonzero (the client is
supposed to call this routine immediately following the lock).
This will cause a well-behaved client to synchronize with
the remaining unreported changes */
return (dgawin->changeMask);
}
static void
{
}
/*
** Returns nonzero if we are still not synchronized
*/
static int
{
/* if a multibuffer change happened, we're still not done */
return (1);
}
/* Note: there's no need to check cacheseq because the effective lock subject
of a window can only be a window or viewable multibuffer.
Neither of these are cached */
return (0);
}
/* Note: viewable mbuf never has bstore to sync up to */
return (0);
}
} else {
/* should never happen */
assert(0);
}
/* we're not synchronized; need to go around the loop again */
return (1);
}
/*
** Called at window lock time when we have detected an mbufset change.
** At the return of this routine, dgawin->eLockSubj indicates the member
** drawable for which subsequent changes are to be detected.
*/
static void
{
/* react to enable and composition changes */
/* if window is multibuffered we may need synchronization */
/* synchronize with any display buffer change */
/* synchronize render buffer state (if necessary) */
}
/* an mbufset change causes us to report changes to all attrs */
} else {
/* should never happen */
assert(0);
}
}
}
/*
** Determine effective lock subject for a multibuffered window.
*/
static void
{
/* see if there is window aliasing. Window aliasing
can only happen in video flip mode */
/* when the window is aliased, the effective lock subject is the
currently displayed buffer */
/* an alias change causes us to report changes on all attributes */
}
}
}
/*
** Current lock subject is a window. Synchronize with changes.
*/
void
{
/* clip state has changed? */
}
/* cursor state has changed? */
}
/* backing store state has changed? */
}
}
}