diff options
| author | Tor Lillqvist <tml@iki.fi> | 2002-02-17 00:25:05 +0000 |
|---|---|---|
| committer | Tor Lillqvist <tml@src.gnome.org> | 2002-02-17 00:25:05 +0000 |
| commit | bc1ec5c14adf484dc05d1818c99a382f3a6a330f (patch) | |
| tree | 0e20f2f645aedf80a71300c7c322586de685fff2 /gdk/gdk.def | |
| parent | ff612419cd913694ca33a8bb8adc7e6dfe9e7400 (diff) | |
| download | gdk-pixbuf-bc1ec5c14adf484dc05d1818c99a382f3a6a330f.tar.gz | |
Massive changes. Too many to list here, but I'll try a summary:
2002-02-17 Tor Lillqvist <tml@iki.fi>
* gdk/win32/*.c: Massive changes. Too many to list here, but I'll
try a summary:
1) Unify GdkPixmap and GdkImage implementation: For each
GdkPixmap, allocate a GdkImage, and vice versa.
GdkPixmapImplWin32Data has a pointer to the GdkImage.
GdkImage::windowing_data is a pointer to the GdkPixmap.
This simplifies many pixmap and image related functions a lot, and
reduces duplicated code snippets. For instance, there is only one
place in gdk/win32 where CreateDIBSection() is called, in the
function _gdk_win32_new_pixmap(). Converting a bitmap (GdkPixmap)
to a Windows region is almost trivial, with the bitmap bits being
readily accessible in the associated GdkImage.
All blitting between GdkPixmaps, GdkWindows and GdkImages goes
through handled the _gdk_win32_blit() function, which calls
different functions to handle the cases of blitting from pixmaps,
inside windows (scrolling), or from windows, which all require
somewhat different handling.
2) Support 256-color mode. This has long been very broken, now it
works more or less OK. Keep the logical palette for each colormap
as small as possible while allocating and freeing colors. Select
and realize the logical palette associated with a GdkColormap into
a DC before drawing or blitting.
When the display is in 256-color mode, make it possible for the
user to override the size of the palette(s) used with either the
GDK_WIN32_MAX_COLORS environment variable, or a -max-colors
command line option. It is possible to reduce the palette size all
the way down to using just the 16 static colors (which causes the
system visual to be of type GDK_VISUAL_STATIC_COLOR. This could
possibly be useful if one desperately wants to avoid color
flashing. (Note that in order for this to work properly, an as of
yet not commited fix to gdkrgb.c is needed.)
Handle the palette messages. On WM_PALETTECHANGED, call
UpdateColors() for the given window hierarchy. Do this only if a
window in some other top-level window hierarchy caused the palette
change (realized a palette). Do this max five times in a row (an
arbitrarily chosen limit), though, otherwise redraw by generating
expose events. On WM_QUERYNEWPALETTE, cause a redraw of the whole
window hierarchy by generating GDK_EXPOSE events.
3) Code cleanup in general. For instance, remove the "emulated"
X11 structs ColormapStruct, Visual and XStandardColormap. Use the
new GDK_DEBUG_* flags for debugging output in the relevant source
files. Remove the unused colormap hash table in gdkcolor-win32.c
4) Plug some resource leaks.
2002-02-14 Tor Lillqvist <tml@iki.fi>
* gdk/win32/gdkdnd-win32.c (gdk_dropfiles_filter): Use
g_filename_to_uri() to actually create legal URIs in the
text/uri-list data.
Diffstat (limited to 'gdk/gdk.def')
| -rw-r--r-- | gdk/gdk.def | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/gdk/gdk.def b/gdk/gdk.def index 24482ce8f..263456074 100644 --- a/gdk/gdk.def +++ b/gdk/gdk.def @@ -29,7 +29,6 @@ EXPORTS gdk_colormap_get_system_size gdk_colormap_get_type gdk_colormap_get_visual - gdk_colormap_lookup gdk_colormap_new gdk_colormap_query_color gdk_colormap_ref @@ -351,7 +350,6 @@ EXPORTS gdk_visual_get_best_with_type gdk_visual_get_system gdk_visual_get_type - gdk_visual_lookup gdk_visual_type_get_type gdk_wcstombs gdk_win32_drawable_get_handle |