On Tue, 31 Oct 2006 10:26:41 -0800, Carl Worth wrote:
> On Tue, 31 Oct 2006 15:26:35 +0100 (CET), Tim Janik wrote:
> > i.e. using averaging, your numbers include uninteresting outliers
> > that can result from scheduling artefacts (like measuring a whole second
> > for copying a single pixel), and
Hi,
You can do it directly with GDK too.
In this way you can show/hide the cursor whenever you want.
Here's a sample code that worked for me:
GtkWidget *widget;
gchar bits[] = {0};
GdkColor color = {0, 0, 0, 0};
GdkPixmap *pixmap;
GdkCursor *cursor;
gtk_init (&argc, &argv);
widget = gtk_win
I'm not sure this will work, as gdk_cursor_new_from_pixmap() is badly
implemented in gdkdfb (see bug 330420).
cheers
Attilio
Pedro Aguilar wrote:
> Hi,
>
> You can do it directly with GDK too.
> In this way you can show/hide the cursor whenever you want.
> Here's a sample code that worked for
HiThanks for ur help
I make cursor invisible using The DFBARGS paramanater
setting DFBARGS=no-cursor.
thanks once again
On 11/10/06, Mike Emmel <[EMAIL PROTECTED]> wrote:
That will work also.The gdk/x11 way is a clear cursor.Both should work.On 11/9/06, Attilio Fiandrotti <
[EMAIL PROTEC
Hi Jamey,Thanks for all the information!But I am just wondering whether I need to continue the entirely xcb-based Gtk-XCB backend. If necessary, I would like you to have a glance at my code, and any comments would be appreciated.
In addition, I will try to make gdk_window_queue just to iterate the
