Simple question

2008-01-22 Thread iluvlinux

hi
   the GdkWindow member of the Event structure contains the GdkWindow
associated with
a particular widget or the GdkWindow of the top level window?

  I am trying to generate a keypress event (just for experiment purpose)
and i am confused regarding GdkWindow *source field ---  which GdkWindow i
should fill in there?

thanks 
-- 
View this message in context: 
http://www.nabble.com/Simple-question-tp15014925p15014925.html
Sent from the Gtk+ - General mailing list archive at Nabble.com.

___
gtk-list mailing list
gtk-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-list


Re: Simple question

2008-01-22 Thread mmassonnet
On Tue, Jan 22, 2008 at 01:00:12AM -0800, iluvlinux wrote:
> hi

Hello,

>the GdkWindow member of the Event structure contains the GdkWindow
> associated with
> a particular widget or the GdkWindow of the top level window?
> 
>   I am trying to generate a keypress event (just for experiment purpose)
> and i am confused regarding GdkWindow *source field ---  which GdkWindow i
> should fill in there?

Every widgets has a GdkWindow.  To get the top level GdkWindow use
gdk_window_get_toplevel().  If you need the top level window GtkWindow
use gtk_widget_get_toplevel().

> thanks 

mike
___
gtk-list mailing list
gtk-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-list


Re: Simple question

2008-01-22 Thread iluvlinux

hi
i think you didn't get my question
i want to know that if i want to generate my own keypress event
what should the GdkWindow field of event structure should contain?
the toplevel GdkWindow or the widget specific GdkWindow on which 
the keypress event actually occurred


bye

mmassonnet wrote:
> 
> On Tue, Jan 22, 2008 at 01:00:12AM -0800, iluvlinux wrote:
>> hi
> 
> Hello,
> 
>>the GdkWindow member of the Event structure contains the GdkWindow
>> associated with
>> a particular widget or the GdkWindow of the top level window?
>> 
>>   I am trying to generate a keypress event (just for experiment purpose)
>> and i am confused regarding GdkWindow *source field ---  which GdkWindow
>> i
>> should fill in there?
> 
> Every widgets has a GdkWindow.  To get the top level GdkWindow use
> gdk_window_get_toplevel().  If you need the top level window GtkWindow
> use gtk_widget_get_toplevel().
> 
>> thanks 
> 
> mike
> ___
> gtk-list mailing list
> gtk-list@gnome.org
> http://mail.gnome.org/mailman/listinfo/gtk-list
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Simple-question-tp15014925p15015487.html
Sent from the Gtk+ - General mailing list archive at Nabble.com.

___
gtk-list mailing list
gtk-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-list


Re: Simple question

2008-01-22 Thread mmassonnet
On Tue, Jan 22, 2008 at 01:48:35AM -0800, iluvlinux wrote:
> 
> hi
> i think you didn't get my question
> i want to know that if i want to generate my own keypress event
> what should the GdkWindow field of event structure should contain?
> the toplevel GdkWindow or the widget specific GdkWindow on which 
> the keypress event actually occurred

If you want your key presses to work for the whole window, use top
level.

> bye

mike
-- 
http://en.wikipedia.org/wiki/Top_posting
___
gtk-list mailing list
gtk-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-list


Re: Simple question

2008-01-22 Thread iluvlinux

thanks

Also i need to know: does Gdk fills in it with toplevel GdkWindow or widget
specific GdkWindow?


bye



mmassonnet wrote:
> 
> On Tue, Jan 22, 2008 at 01:48:35AM -0800, iluvlinux wrote:
>> 
>> hi
>> i think you didn't get my question
>> i want to know that if i want to generate my own keypress event
>> what should the GdkWindow field of event structure should contain?
>> the toplevel GdkWindow or the widget specific GdkWindow on which 
>> the keypress event actually occurred
> 
> If you want your key presses to work for the whole window, use top
> level.
> 
>> bye
> 
> mike
> -- 
> http://en.wikipedia.org/wiki/Top_posting
> ___
> gtk-list mailing list
> gtk-list@gnome.org
> http://mail.gnome.org/mailman/listinfo/gtk-list
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Simple-question-tp15014925p15016804.html
Sent from the Gtk+ - General mailing list archive at Nabble.com.

___
gtk-list mailing list
gtk-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-list


Problems with keyboard grabbing under GNOME.

2008-01-22 Thread Edward Tomasz Napierala
I'm writing an application - virtual MIDI keyboard - and I'd like
it to be able to grab keys, i.e. to have keyboard events delivered
to it even when it does not have a focus.  The following code demonstrates
problems I had with three approaches I've tried.  All three work[1] under
my simplistic (mostly WindowMaker and XTerm) environment, but fail with
GNOME.  I didn't test it under KDE yet.

Can somebody advise me how to do this correctly?  Thanks :-)


[1]. Ok, there is minor glitch with XGrabKey - key release events seem
 to get lost, but that seems to be Xorg issue.



/* Example code to demonstrate problems with keyboard grabbing. */
/* Edward Tomasz Napierala <[EMAIL PROTECTED]>, January 2008 */

/* $XConsortium: xev.c,v 1.15 94/04/17 20:45:20 keith Exp $ */
/*

   Copyright (c) 1988  X Consortium

   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, and/or sell copies of the Software, and to
   permit persons to whom the Software is furnished to do so, subject to
   the following conditions:

   The above copyright notice and this permission notice 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 X CONSORTIUM 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.

   Except as contained in this notice, the name of the X Consortium shall
   not be used in advertising or otherwise to promote the sale, use or
   other dealings in this Software without prior written authorization
   from the X Consortium.

 */
/* $XFree86: xc/programs/xev/xev.c,v 1.13 2003/10/24 20:38:17 tsi Exp $ */

/*
 * Author:  Jim Fulton, MIT X Consortium
 */

#include 
#include 
#include 
#include 
#include 
#include 
#include 

const char *Yes = "YES";
const char *No = "NO";
const char *Unknown = "unknown";

Display *dpy;
int screen;

static void
prologue (XEvent *eventp, char *event_name)
{
XAnyEvent *e = (XAnyEvent *) eventp;

printf ("\n%s event, serial %ld, synthetic %s, window 0x%lx,\n",
event_name, e->serial, e->send_event ? Yes : No, 
e->window);
}

static void
dump (char *str, int len)
{
printf("(");
len--;
while (len-- > 0)
printf("%02x ", (unsigned char) *str++);
printf("%02x)", (unsigned char) *str++);
}

static void
do_KeyPress (XEvent *eventp)
{
XKeyEvent *e = (XKeyEvent *) eventp;
KeySym ks;
KeyCode kc = 0;
Bool kc_set = False;
char *ksname;
int nbytes;
char str[256+1];
static char *buf = NULL;
static int bsize = 8;

if (buf == NULL)
buf = malloc (bsize);

nbytes = XLookupString (e, str, 256, &ks, NULL);

if (ks == NoSymbol)
ksname = "NoSymbol";
else {
if (!(ksname = XKeysymToString (ks)))
ksname = "(no name)";
kc = XKeysymToKeycode(dpy, ks);
kc_set = True;
}

printf ("root 0x%lx, subw 0x%lx, time %lu, (%d,%d), 
root:(%d,%d),\n",
e->root, e->subwindow, e->time, e->x, e->y, e->x_root, 
e->y_root);
printf ("state 0x%x, keycode %u (keysym 0x%lx, %s), same_screen 
%s,\n",
e->state, e->keycode, (unsigned long) ks, ksname,
e->same_screen ? Yes : No);
if (kc_set && e->keycode != kc)
printf ("XKeysymToKeycode returns keycode: %u\n",kc);
if (nbytes < 0) nbytes = 0;
if (nbytes > 256) nbytes = 256;
str[nbytes] = '\0';
printf ("XLookupString gives %d bytes: ", nbytes);
if (nbytes > 0) {
dump (str, nbytes);
printf (" \"%s\"\n", str);
} else {
printf ("\n");
}

printf ("XFilterEvent returns: %s\n", 
XFilterEvent (eventp, e->window) ? "True" : "False");
}

static void
do_KeyRelease (XEvent *eventp)
{
do_KeyPress (eventp);   /* since it has the same info */
}

int
main (int argc, char **argv)
{
int i;

dpy = XOpenDisplay (NULL);
if (!dpy) {
fprintf (stderr, "Unable to open display.\n");
exit (1);
}

screen = DefaultScreen (dpy);

#if defined(XGRABKEY)
/*
 * Problem #1: This won't work at all unde

Re: Newbie Question about Navigating API doco

2008-01-22 Thread Pablo Yanez Trujillo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hello

Navigating the API doc is very easy once you've understood how it is organised.

The API is divided in 5 main topics. I think the first three are the one that 
are most used.

Topic 1, GTK+ Overview: gives you the overview of GTK+, i.e. what it is and how 
you can use it under different
environments like Windows and Unix-like systems.

Topic 2, GTK+ Core Reference: this is perhaps not the best part to start with 
because there are sometimes concepts that
you understand later, when you have written some (little) GTK+ application. It 
conatains also main concepts that are
widely used in the widgets. As a newbie I would read "Main loop and Events", 
"Signals" and "Types".

Topic 3, GTK+ Widgets and Objects: here you have the documentation of the GTK+ 
Widgets you can use in your apps. This is
far more a listing of constants, functions, macros, signals, properties, etc. 
that are declared within the widgets. Some
widgets have explanations about how to use them but it cannot replace a good 
old tutorial  :)  At the top of each widget
page you'll find a navigation bar with which you can navigate quickly through 
the page.

Sometimes you see something and you don't have a clue where it belongs nor 
where to search for it. On the bottom of the
start page you'll find a link to the "index" page. You'll find there a (more or 
less) complete list of the actual
constants, functions, macros, signals, properties, etc.

> The point is, if say in the helloWorld program in the
> tutorial I change all instances of the string "delete_event" to
> "monkey" the program still compiles.

Do you also have changed this line

  g_signal_connect (G_OBJECT (window), "delete_event",
  G_CALLBACK (delete_event), NULL);

to

  g_signal_connect (G_OBJECT (window), "monkey",
  G_CALLBACK (monkey), NULL);
???

If so then you did a mistake. The second argument of the g_signal_connect 
function expects the name of a signal
(internal name of the signal in GTK+, not the name of a function) and there 
isn't a "monkey" signal, hence you get the
message that the signal `monkey' is invalid.

> I can't find a reference to "delete_event" in the API.  But possibly
> not looking in the right place.

I'm afraid so  :)  each widget has it own delete_event that is inherited from 
the GtkWidget class. Hence you will find the
documentation of this particular signal under the GtkWidget page. If you would 
have searched it in the "index" page you
would have found it  :)

http://library.gnome.org/devel/gtk/unstable/GtkWidget.html#id4180743

Regards

Pablo

Pablo Yanez Trujillo
http://klingsor.informatik.uni-freiburg.de
My public key: http://klingsor.informatik.uni-freiburg.de/gpg/supertux.asc


Peter E Dennis wrote:
> Hi All,
> 
> I am just starting out and going through the tutorial.  I was
> wondering where I could find other signal strings like "delete_event"
> in the api?
> 
> I noticed that it is defined in gtkwidget.c
> 
> Do I need to know this kind of stuff?
> 
> Sorry about the vague question, don't know enough to ask about it
> properly.  The point is, if say in the helloWorld program in the
> tutorial I change all instances of the string "delete_event" to
> "monkey" the program still compiles.  When I run it though I get:
> 
> $ ./helloWorld
> (helloWorld:): GLib-GObject-WARNING **:
> /build/buildd/glib2.0-2.14.1/gobject/gsignal.c:1669: signal `monkey'
> is invalid for instance `0x8077000'
> 
> I can't find a reference to "delete_event" in the API.  But possibly
> not looking in the right place.  Can someone point me to it and others
> like it for other widgets?
> 
> Many thanks,
> 
> Peter.
> ___
> gtk-list mailing list
> gtk-list@gnome.org
> http://mail.gnome.org/mailman/listinfo/gtk-list
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHlgnNDzf8xo+0xRURAkbXAKCojQ25bFtEZamRuqmAdUcZJe6wnQCeLHaS
yISe7sWCaLM5GI6M1V49x8A=
=Bp4C
-END PGP SIGNATURE-
___
gtk-list mailing list
gtk-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-list


Re: GLib 2.15.3 released

2008-01-22 Thread Pavan Kumar Reddy
  Hi All,

Iam using glib api's (g_convert)to convert the UTF-8 to ISO-8859-1..
but it displayed error as "Coversion from UTF-8 to ISO-8859-1 is not supported"


For me its working fine in linux, but when i port my code in embedded..this 
g_convert fails  and displays error..
 
Is anybody knows how to solve this problem..

Regards
Pavan Reddy.

On Tue, 22 Jan 2008 Matthias Clasen wrote :
>GLib 2.15.3 is now available for download at:
>
>http://ftp.gnome.org/pub/GNOME/sources/glib/2.15/
>
>glib-2.15.3.tar.bz2 md5sum: 83aa09c6126e3111c9f371c1396324e7
>glib-2.15.3.tar.gz  md5sum: c6e6310e1a8d2eb85e043cc9408486c6
>
>This is the fourth development release leading up to GLib 2.16.
>
>Notes:
>
>  * This is unstable development release. While it has had
>a bit of testing, there are certainly plenty of bugs
>remaining to be found. This release should not be used
>in production.
>
>  * Installing this version will overwrite your existing
>copy of GLib 2.14. If you have problems, you'll need
>to reinstall GLib 2.14.
>
>  * GLib 2.16 will be source and binary compatible with
>the GLib 2.14 series. The new API in GLib should be
>stable at this point; we are still expecting to do
>some minor API additions in GIO, so there may be
>incompatibilities between this release and the final
>2.16 release.
>
>  * Bugs should be reported to http://bugzilla.gnome.org.
>
>
>About GLib
>==
>
>GLib is the low-level core library that forms the basis for projects
>such as GTK+ and GNOME. It provides data structure handling for C,
>portability wrappers, and interfaces for such runtime functionality as
>an event loop, threads, dynamic loading, and an object system.
>
>More information about GLib is available at:
>
>  http://www.gtk.org/
>
>An installation guide for the GTK+ libraries, including GLib, can
>be found at:
>
>  http://developer.gnome.org/doc/API/2.0/gtk/gtk-building.html
>
>
>Overview of Changes from GLib 2.15.2 to GLib 2.15.3
>===
>
>* GChecksum:
>  - g_checksum_update can accept nul-terminated strings
>  - The MD5 implementation works correctly on buffers
>that are longer than 64 bytes
>
>* GIO:
>  - Don't include a copy of the inotify headers, rely on system headers
>  - g_file_find_enclosing_mount has an async variant now
>  - Reduntant seek API on file streams has been removed
>
>* Bugs fixed:
>   508602 gmemory{in|out}putstream.c: unknown pointer size
>   508771 There is no g_file_test/exists() for GFile
>   508773 g_uri_escape_string() documentation unclear.
>   509465 AM_PATH_GLIB_2_0 doesn't support gio
>   509626 async functions: Document allowed NULL callback?
>   509990 GSeekable documentation unclear
>   510448 No inotify support on ARM or SH5
>   510855 g_checksum_update(): Take -1 for length.
>
>* Updated translations:
>   Basque (eu)
>   Marathi (mr)
>   Swedish (sv)
>   Ukrainian (uk)
>
>
>A list of all fixed bugs can be found here:
>http://bugzilla.gnome.org/buglist.cgi?bug_id=508773,509465,510855,508602,509626,508771,510448,509990
>
>
>Thanks to all contributors
>Dan Winship
>Alexander Larsson
>Murray Cumming
>Tim Janik
>Kazuki IWAMOTO
>
>
>January 21, 2008
>Matthias Clasen
>
>
>___
>gtk-list mailing list
>gtk-list@gnome.org
>http://mail.gnome.org/mailman/listinfo/gtk-list
___
gtk-list mailing list
gtk-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-list


Re: GLib 2.15.3 released

2008-01-22 Thread Matthias Clasen
On 22 Jan 2008 16:45:10 -, Pavan Kumar Reddy
<[EMAIL PROTECTED]> wrote:
>  Hi All,
>
> Iam using glib api's (g_convert)to convert the UTF-8 to ISO-8859-1..
> but it displayed error as "Coversion from UTF-8 to ISO-8859-1 is not 
> supported"
>
>
> For me its working fine in linux, but when i port my code in embedded..this 
> g_convert fails  and displays error..
>
> Is anybody knows how to solve this problem..
>

g_convert supports whatever the underlying iconv implementation supports.
___
gtk-list mailing list
gtk-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-list


Re: Newbie Question about Navigating API doco

2008-01-22 Thread Peter E Dennis
Hi Pablo,

Thank you for the great overview of the documentation and pointing me
towards the index.  When I follow that link you provided to
information about the delete_event it actually displays it as:

The "delete-event" signal.

Rather than:

The "delete_event" signal

I am sorry for being pedantic but this would make me believe when
reading the documentation that I was to use "delete-event" in my
program with a hyphen '-' not with an underscore '_'

Is this standard notation in the documentation?  Should I be reading
any signals I see that contain a hyphen to substitute this with an
underscore when it is written in code?

Thanks again for your help.

Peter.

On 23/01/2008, Pablo Yanez Trujillo <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hello
>
> Navigating the API doc is very easy once you've understood how it is 
> organised.
>
> The API is divided in 5 main topics. I think the first three are the one that 
> are most used.
>
> Topic 1, GTK+ Overview: gives you the overview of GTK+, i.e. what it is and 
> how you can use it under different
> environments like Windows and Unix-like systems.
>
> Topic 2, GTK+ Core Reference: this is perhaps not the best part to start with 
> because there are sometimes concepts that
> you understand later, when you have written some (little) GTK+ application. 
> It conatains also main concepts that are
> widely used in the widgets. As a newbie I would read "Main loop and Events", 
> "Signals" and "Types".
>
> Topic 3, GTK+ Widgets and Objects: here you have the documentation of the 
> GTK+ Widgets you can use in your apps. This is
> far more a listing of constants, functions, macros, signals, properties, etc. 
> that are declared within the widgets. Some
> widgets have explanations about how to use them but it cannot replace a good 
> old tutorial  :)  At the top of each widget
> page you'll find a navigation bar with which you can navigate quickly through 
> the page.
>
> Sometimes you see something and you don't have a clue where it belongs nor 
> where to search for it. On the bottom of the
> start page you'll find a link to the "index" page. You'll find there a (more 
> or less) complete list of the actual
> constants, functions, macros, signals, properties, etc.
>
> > The point is, if say in the helloWorld program in the
> > tutorial I change all instances of the string "delete_event" to
> > "monkey" the program still compiles.
>
> Do you also have changed this line
>
>   g_signal_connect (G_OBJECT (window), "delete_event",
>   G_CALLBACK (delete_event), NULL);
>
> to
>
>   g_signal_connect (G_OBJECT (window), "monkey",
>   G_CALLBACK (monkey), NULL);
> ???
>
> If so then you did a mistake. The second argument of the g_signal_connect 
> function expects the name of a signal
> (internal name of the signal in GTK+, not the name of a function) and there 
> isn't a "monkey" signal, hence you get the
> message that the signal `monkey' is invalid.
>
> > I can't find a reference to "delete_event" in the API.  But possibly
> > not looking in the right place.
>
> I'm afraid so  :)  each widget has it own delete_event that is inherited from 
> the GtkWidget class. Hence you will find the
> documentation of this particular signal under the GtkWidget page. If you 
> would have searched it in the "index" page you
> would have found it  :)
>
> http://library.gnome.org/devel/gtk/unstable/GtkWidget.html#id4180743
>
> Regards
>
> Pablo
>
> Pablo Yanez Trujillo
> http://klingsor.informatik.uni-freiburg.de
> My public key: http://klingsor.informatik.uni-freiburg.de/gpg/supertux.asc
>
>
> Peter E Dennis wrote:
> > Hi All,
> >
> > I am just starting out and going through the tutorial.  I was
> > wondering where I could find other signal strings like "delete_event"
> > in the api?
> >
> > I noticed that it is defined in gtkwidget.c
> >
> > Do I need to know this kind of stuff?
> >
> > Sorry about the vague question, don't know enough to ask about it
> > properly.  The point is, if say in the helloWorld program in the
> > tutorial I change all instances of the string "delete_event" to
> > "monkey" the program still compiles.  When I run it though I get:
> >
> > $ ./helloWorld
> > (helloWorld:): GLib-GObject-WARNING **:
> > /build/buildd/glib2.0-2.14.1/gobject/gsignal.c:1669: signal `monkey'
> > is invalid for instance `0x8077000'
> >
> > I can't find a reference to "delete_event" in the API.  But possibly
> > not looking in the right place.  Can someone point me to it and others
> > like it for other widgets?
> >
> > Many thanks,
> >
> > Peter.
> > ___
> > gtk-list mailing list
> > gtk-list@gnome.org
> > http://mail.gnome.org/mailman/listinfo/gtk-list
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFHlgnNDzf8xo+0xRURAkbXAKCojQ25bFtEZamRuqmAdUcZJe6wnQCeLHaS
> yISe7sWCaLM5GI6M1V49x8A=
> =Bp4C
> -END PGP SIGNATURE-
> ___

gtk2.8.20

2008-01-22 Thread Darko
Hi
I wish to make Gtk 2.8.20, but request me beatwen all Cairo i Atk, and 
now stands a problems
Cairo makes me following mistake (error)

/tmp/ccI1Jeqi.s: Assembler messages:
/tmp/ccI1Jeqi.s:8651: Error: symbol `_cairo_pixman_composite' is already 
defined
make[3]: *** [fbpict.lo] Greška 1 (<=Stands for error 1 )
make[3]: Izlazim iz direktorija `/home/darko/GtkT/cairo-1.0.2/pixman/src'
make[2]: *** [all-recursive] Greška 1 (<=Stands for error 1 )
make[2]: Izlazim iz direktorija `/home/darko/GtkT/cairo-1.0.2/pixman'
make[1]: *** [all-recursive] Greška 1 (<=Stands for error 1 )
make[1]: Izlazim iz direktorija `/home/darko/GtkT/cairo-1.0.2'
make: *** [all] Greška 2 (<=Stands for error 2 )
localhost:/home/darko/GtkT/cairo-1.0.2#airo
/tmp/ccI1Jeqi.s: Assembler messages:
/tmp/ccI1Jeqi.s:8651: Error: symbol `_cairo_pixman_composite' is already 
defined
make[3]: *** [fbpict.lo] Greška 1 (<=Stands for error 1 )
make[3]: Izlazim iz direktorija `/home/darko/GtkT/cairo-1.0.2/pixman/src'
make[2]: *** [all-recursive] Greška 1 (<=Stands for error 1 )
make[2]: Izlazim iz direktorija `/home/darko/GtkT/cairo-1.0.2/pixman'
make[1]: *** [all-recursive] Greška 1 (<=Stands for error 1 )
make[1]: Izlazim iz direktorija `/home/darko/GtkT/cairo-1.0.2'
make: *** [all] Greška 2 (<=Stands for error 2)
localhost:/home/darko/GtkT/cairo-1.0.2#


ant atk list me this

checking for GLIB - version >= 2.5.7...
*** 'pkg-config --modversion glib-2.0' returned 2.8.6, but GLIB (2.12.4)
*** was found! If pkg-config was correct, then it is best
*** to remove the old version of GLib. You may also be able to fix the 
error
*** by modifying your LD_LIBRARY_PATH enviroment variable, or by editing
*** /etc/ld.so.conf. Make sure you have run ldconfig if that is
*** required on your system.
*** If pkg-config was wrong, set the environment variable PKG_CONFIG_PATH
*** to point to the correct configuration files
no
checking for pkg-config... (cached) /usr/local/bin/pkg-config
checking for GLIB - version >= 2.0.0...
*** 'pkg-config --modversion glib-2.0' returned 2.8.6, but GLIB (2.12.4)
*** was found! If pkg-config was correct, then it is best
*** to remove the old version of GLib. You may also be able to fix the 
error
*** by modifying your LD_LIBRARY_PATH enviroment variable, or by editing
*** /etc/ld.so.conf. Make sure you have run ldconfig if that is
*** required on your system.
*** If pkg-config was wrong, set the environment variable PKG_CONFIG_PATH
*** to point to the correct configuration files
no
configure: error:
*** GLIB 2.0.0 or better is required. The latest version of
*** GLIB is always available from ftp://ftp.gtk.org/. If GLIB is installed
*** but not in the same location as pkg-config add the location of the file
*** glib-2.0.pc to the environment variable PKG_CONFIG_PATH.

I instaled glib 2.8.6 from source tar.gz not knowing that maybe with 
debian come glib2.12.4




How to bulid gtk?

-- 


Darko.
Linux debian-etch 2.6.18-5-686 # i686 GNU/Linux 

"I'm not a vegetarian because I love animals, I'm a vegetarian because I hate 
vegetables!"
unknown 

___
gtk-list mailing list
gtk-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-list


Re: Newbie Question about Navigating API doco

2008-01-22 Thread Mathias Hasselmann

Am Mittwoch, den 23.01.2008, 06:04 +1100 schrieb Peter E Dennis:
> I am sorry for being pedantic but this would make me believe when
> reading the documentation that I was to use "delete-event" in my
> program with a hyphen '-' not with an underscore '_'
> 
> Is this standard notation in the documentation?  Should I be reading
> any signals I see that contain a hyphen to substitute this with an
> underscore when it is written in code?

Whether you use hyphen or underscore is a matter of personal preference,
both variants work.

Ciao,
Mathias
-- 
Mathias Hasselmann <[EMAIL PROTECTED]>
Openismus GmbH: http://www.openismus.com/
Personal Site: http://taschenorakel.de/


signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
___
gtk-list mailing list
gtk-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-list


Re: Newbie Question about Navigating API doco

2008-01-22 Thread Peter E Dennis
Thanks for clearing that up Mathias.  Really appreciate it.

On 23/01/2008, Mathias Hasselmann <[EMAIL PROTECTED]> wrote:
>
> Am Mittwoch, den 23.01.2008, 06:04 +1100 schrieb Peter E Dennis:
> > I am sorry for being pedantic but this would make me believe when
> > reading the documentation that I was to use "delete-event" in my
> > program with a hyphen '-' not with an underscore '_'
> >
> > Is this standard notation in the documentation?  Should I be reading
> > any signals I see that contain a hyphen to substitute this with an
> > underscore when it is written in code?
>
> Whether you use hyphen or underscore is a matter of personal preference,
> both variants work.
>
> Ciao,
> Mathias
> --
> Mathias Hasselmann <[EMAIL PROTECTED]>
> Openismus GmbH: http://www.openismus.com/
> Personal Site: http://taschenorakel.de/
>
>
___
gtk-list mailing list
gtk-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-list


GTKSourceview + PyGTKSourceview for Windows

2008-01-22 Thread Kevin Goodspeed
I downloaded GTKSourceview and PyGTKSourceview from
http://code.google.com/p/bpad/wiki/GtksourceviewForWindows
but I don't know where the files need to go for GTK+ and Python to use
them.  Any ideas?

- CircuitsMan
___
gtk-list mailing list
gtk-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-list


Re: gtk2.8.20

2008-01-22 Thread Sergei Steshenko

--- Darko <[EMAIL PROTECTED]> wrote:

> Hi
> I wish to make Gtk 2.8.20,
[snip]

Do you really want the outdated gtk-2.8.20 ?

Maybe you'll be interested to build gtk+-2.12.5 - the "latest and greatest"
stable one ?

--Sergei.

Applications From Scratch: http://appsfromscratch.berlios.de/


  

Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ 

___
gtk-list mailing list
gtk-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-list