Thanks for your answer.
I did a stand alone gtk application build on an OS window7.
I installed it manually on an other computer run with window 7. I copyed all the needed dynamic (.DLL) libraries in the directory where my application (.exe) was installed.
My application worked perfectly. It may be important to notice that on this new computer GTK was'nt installed .
Then, i did the same thing on 2 different computers run with window VISTA. I Get an error message, in French. The English translation might be:
This application can't start because API-MS-WIN-CORE-LOCALREGISTRY-L1-1-0.DLL is missing (or can't be find)....
On the web I finded this library and an other one (API-MS-WIN-CORE-ERRORHANDLING-L1-1-0.DLL). I put them in the directory where my application was installed. I get a new message:
This application application can't start because API-MS-WIN-CORE-HANDLE-L1-1-0.DLL is missing (or can't be find)....
I Could'nt find it on the web.
I could notice that any of API-MS-WIN-CORE.... libraries are installed on VISTA.
Once again, many thanks for your help.
> Message du 11/05/15 23:45
> De : gtk-list-request gnome org
> A : gtk-list gnome org
> Copie à :
> Objet : gtk-list Digest, Vol 133, Issue 10
>
> Send gtk-list mailing list submissions to
> gtk-list gnome org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://mail.gnome.org/mailman/listinfo/gtk-list
> or, via email, send a message with subject or body 'help' to
> gtk-list-request gnome org
>
> You can reach the person managing the list at
> gtk-list-owner gnome org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of gtk-list digest..."
>
>
> Today's Topics:
>
> 1. (Bernard CANTALOUBE)
> 2. Re: API-MS-WIN-CORE (Mihamina Rakotomandimby)
> 3. In GTK, how are screen coordinates mapped to GUI objects?
> (George Nychis)
> 4. Re: In GTK, how are screen coordinates mapped to GUI objects?
> (Jasper St. Pierre)
> 5. Re: In GTK, how are screen coordinates mapped to GUI objects?
> (Paul Davis)
> 6. Re: In GTK, how are screen coordinates mapped to GUI objects?
> (Paul Davis)
> 7. Re: In GTK, how are screen coordinates mapped to GUI objects?
> (Jasper St. Pierre)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 11 May 2015 16:16:49 +0200 (CEST)
> From: Bernard CANTALOUBE <bernard cantaloube wanadoo fr>
> To: gtk-list gnome org
> Message-ID: <878926418 21682 1431353809089 JavaMail www wwinf1p09>
> Content-Type: text/plain; charset="utf-8"
>
> I have a problem with window VISTA:
>
> ?
>
> All the libraries API-MS-WIN-CORE..... are missing.
>
> ?
>
> A stand alone application made with GTK can't work withou them.
>
> ?
>
> Is there a solution ?
>
> ?
>
> Thanks.?
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <https://mail.gnome.org/archives/gtk-list/attachments/20150511/96913b64/attachment.html>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 11 May 2015 20:38:03 +0300
> From: Mihamina Rakotomandimby <mihamina rakotomandimby rktmb org>
> To: gtk-list gnome org
> Subject: Re: API-MS-WIN-CORE
> Message-ID: <5550E8FB 6070403 rktmb org>
> Content-Type: text/plain; charset=windows-1252; format=flowed
>
> On 05/11/2015 05:16 PM, Bernard CANTALOUBE wrote:
> >
> > I have a problem with window VISTA:
> >
> > All the libraries API-MS-WIN-CORE..... are missing.
> >
> > A stand alone application made with GTK can't work withou them.
> >
> > Is there a solution ?
> >
>
> More details needed:
> What did you install, how did you install?
> What are you trying to run?
> What is the error message?
>
> Thank you.
>
>
>
>
> ------------------------------
>
> Message: 3
> Date: Mon, 11 May 2015 17:14:09 -0400
> From: George Nychis <gnychis gmail com>
> To: gtk-list gnome org
> Subject: In GTK, how are screen coordinates mapped to GUI objects?
> Message-ID:
> <CA+7oygc7tPSmCTJ2zvucXCzS-1TM=+qLpRtrmFVbDSYjmVwh2Q mail gmail com>
> Content-Type: text/plain; charset="utf-8"
>
> I am trying to gain a very technical understanding of how operating systems
> and GUI systems (like GTK) scalably map coordinates on the 2d screen to
> objects. For example, there are many applications running with graphical
> interfaces to them active on the screen, and each application interface has
> dozens (if not hundreds) of objects (buttons, scroll bars, etc.). Some
> objects are contained within other objects.
>
> So, what I am trying to learn more about is how something like GTK maps a
> screen coordinate (and an action like a mouse click) to an object quickly
> to generate a callback to the appropriate application or object. In
> particular, when there are objects within objects, how it narrows the
> search down to the "smallest" element that your mouse is hovering over when
> a click event fired.
>
> I'd love to know about what data structures and algorithms are used to
> perform this mapping between the 2D graphical space to objects.
>
> Thanks!
> George
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <https://mail.gnome.org/archives/gtk-list/attachments/20150511/9d3a1812/attachment.html>
>
> ------------------------------
>
> Message: 4
> Date: Mon, 11 May 2015 14:30:43 -0700
> From: "Jasper St. Pierre" <jstpierre mecheye net>
> To: George Nychis <gnychis gmail com>
> Cc: "gtk-list gnome org" <gtk-list gnome org>
> Subject: Re: In GTK, how are screen coordinates mapped to GUI objects?
> Message-ID:
> <CAA0H+QTmCSG7=Amk-zohpvzE_TzMmO2sgVb3MmJAfsCpDnxdLA mail gmail com>
> Content-Type: text/plain; charset=UTF-8
>
> Computers are *fast*. It turns out that simply recursively walking
> down all children is fast enough for most cases. It's a complicated
> walk, but it's entirely doable. You can see the code for the walk
> here:
>
> https://git.gnome.org/browse/gtk+/tree/gdk/gdkwindow.c#n7247
>
> More complex data structures, like a map of pixel to object, would
> take up too much memory, or require too much effort to suitably parse.
> The simple and brute force solution often works well, because you'll
> never have more than 100 visible children in the worst case, and 100
> is not a big enough number to optimize for.
>
> On Mon, May 11, 2015 at 2:14 PM, George Nychis <gnychis gmail com> wrote:
> > I am trying to gain a very technical understanding of how operating systems
> > and GUI systems (like GTK) scalably map coordinates on the 2d screen to
> > objects. For example, there are many applications running with graphical
> > interfaces to them active on the screen, and each application interface has
> > dozens (if not hundreds) of objects (buttons, scroll bars, etc.). Some
> > objects are contained within other objects.
> >
> > So, what I am trying to learn more about is how something like GTK maps a
> > screen coordinate (and an action like a mouse click) to an object quickly to
> > generate a callback to the appropriate application or object. In
> > particular, when there are objects within objects, how it narrows the search
> > down to the "smallest" element that your mouse is hovering over when a click
> > event fired.
> >
> > I'd love to know about what data structures and algorithms are used to
> > perform this mapping between the 2D graphical space to objects.
> >
> > Thanks!
> > George
> >
> > _______________________________________________
> > gtk-list mailing list
> > gtk-list gnome org
> > https://mail.gnome.org/mailman/listinfo/gtk-list
> >
>
>
>
> --
> Jasper
>
>
> ------------------------------
>
> Message: 5
> Date: Mon, 11 May 2015 17:37:31 -0400
> From: Paul Davis <paul linuxaudiosystems com>
> To: "Jasper St. Pierre" <jstpierre mecheye net>
> Cc: "gtk-list gnome org" <gtk-list gnome org>
> Subject: Re: In GTK, how are screen coordinates mapped to GUI objects?
> Message-ID:
> <CAFa_cK=fOpmN03ZajejG2ewC1K5UvQyEkXhdLARqR2Gzt6Ezaw mail gmail com>
> Content-Type: text/plain; charset="utf-8"
>
> On Mon, May 11, 2015 at 5:30 PM, Jasper St. Pierre <jstpierre mecheye net>
> wrote:
>
> > Computers are *fast*. It turns out that simply recursively walking
> > down all children is fast enough for most cases. It's a complicated
> > walk, but it's entirely doable. You can see the code for the walk
> > here:
> >
> > https://git.gnome.org/browse/gtk+/tree/gdk/gdkwindow.c#n7247
> >
>
>
> notice the assumption that there's no Z-axis ordering. this is important
> and simplifies the code/algorithm significantly. many modern applications
> occupy what we might call "2-1/2D", where the 3rd dimension doesn't
> represent real space, but the stacking of items does have some semantic
> significance.
>
> the tree walking algorithm also causes issues with any situations (which
> admittedly are rare) where objects are highly non-rectangular.
>
>
> >
> > More complex data structures, like a map of pixel to object, would
> > take up too much memory, or require too much effort to suitably parse.
> > The simple and brute force solution often works well, because you'll
> > never have more than 100 visible children in the worst case, and 100
> > is not a big enough number to optimize for.
> >
>
> this number isn't realistic in the more general case where the "things" on
> the screen are less heavy-weight than widgets. So certainly it works OK for
> the GDK/GTK case, but in terms of a general mapping, optimizations do and
> can matter. A typical somewhat complex session in Ardour that involves MIDI
> and audio data might have in excess of 2k objects on the screen, and in
> extreme cases, a factor of ten larger.
>
> unfortunately, the map of pixel to object is also too expensive in that
> case. we don't have the right answer (yet), so we too walk the tree, but we
> have to take layering (z-axis) into account. it easy to see this slow down
> certain aspects of GUI performance.
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <https://mail.gnome.org/archives/gtk-list/attachments/20150511/ff3c7da0/attachment.html>
>
> ------------------------------
>
> Message: 6
> Date: Mon, 11 May 2015 17:39:25 -0400
> From: Paul Davis <paul linuxaudiosystems com>
> To: "Jasper St. Pierre" <jstpierre mecheye net>
> Cc: "gtk-list gnome org" <gtk-list gnome org>
> Subject: Re: In GTK, how are screen coordinates mapped to GUI objects?
> Message-ID:
> <CAFa_cKkpMpYcW3YAriQZDsZuE4QLcpU0AzpoHqYfm1tfiHgUaA mail gmail com>
> Content-Type: text/plain; charset="utf-8"
>
> On Mon, May 11, 2015 at 5:30 PM, Jasper St. Pierre <jstpierre mecheye net>
> > wrote:
> >
> >>
> >> https://git.gnome.org/browse/gtk+/tree/gdk/gdkwindow.c#n7247
> >>
> >
> >
> > notice the assumption that there's no Z-axis ordering.
> >
>
> that will teach me to write first and read second. GDK in GTK3 now does
> have z-axis ordering even though the semantics of this are still not fully
> defined, as i understand it.
>
> stupid me. too mired in the GTK2 world. sorry for the noise on that point.
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <https://mail.gnome.org/archives/gtk-list/attachments/20150511/eb66291a/attachment.html>
>
> ------------------------------
>
> Message: 7
> Date: Mon, 11 May 2015 14:44:58 -0700
> From: "Jasper St. Pierre" <jstpierre mecheye net>
> To: Paul Davis <paul linuxaudiosystems com>
> Cc: "gtk-list gnome org" <gtk-list gnome org>
> Subject: Re: In GTK, how are screen coordinates mapped to GUI objects?
> Message-ID:
> <CAA0H+QRGjxkpYM6ha=CLW+FNq+-USmVh+L001C1dMpaZdOKQMw mail gmail com>
> Content-Type: text/plain; charset=UTF-8
>
> Right. If you were building a scalable UI with a flat hierarchy of
> objects that do not move often (scrolling is OK, since scrolling is
> just an offset across the whole set of objects), then one solution is
> known as a quadtree. The idea here is that you recursively subdivide
> the scene into quadrants and try to balance it such that each quadrant
> has 5-10 objects. You spend a lot more time building the quadtree but
> it will significantly cut down on lookup time.
>
> On Mon, May 11, 2015 at 2:37 PM, Paul Davis <paul linuxaudiosystems com> wrote:
> >
> >
> > On Mon, May 11, 2015 at 5:30 PM, Jasper St. Pierre <jstpierre mecheye net>
> > wrote:
> >>
> >> Computers are *fast*. It turns out that simply recursively walking
> >> down all children is fast enough for most cases. It's a complicated
> >> walk, but it's entirely doable. You can see the code for the walk
> >> here:
> >>
> >> https://git.gnome.org/browse/gtk+/tree/gdk/gdkwindow.c#n7247
> >
> >
> >
> > notice the assumption that there's no Z-axis ordering. this is important and
> > simplifies the code/algorithm significantly. many modern applications occupy
> > what we might call "2-1/2D", where the 3rd dimension doesn't represent real
> > space, but the stacking of items does have some semantic significance.
> >
> > the tree walking algorithm also causes issues with any situations (which
> > admittedly are rare) where objects are highly non-rectangular.
> >
> >>
> >>
> >> More complex data structures, like a map of pixel to object, would
> >> take up too much memory, or require too much effort to suitably parse.
> >> The simple and brute force solution often works well, because you'll
> >> never have more than 100 visible children in the worst case, and 100
> >> is not a big enough number to optimize for.
> >
> >
> > this number isn't realistic in the more general case where the "things" on
> > the screen are less heavy-weight than widgets. So certainly it works OK for
> > the GDK/GTK case, but in terms of a general mapping, optimizations do and
> > can matter. A typical somewhat complex session in Ardour that involves MIDI
> > and audio data might have in excess of 2k objects on the screen, and in
> > extreme cases, a factor of ten larger.
> >
> > unfortunately, the map of pixel to object is also too expensive in that
> > case. we don't have the right answer (yet), so we too walk the tree, but we
> > have to take layering (z-axis) into account. it easy to see this slow down
> > certain aspects of GUI performance.
> >
> >
> >
>
>
>
> --
> Jasper
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> gtk-list mailing list
> gtk-list gnome org
> https://mail.gnome.org/mailman/listinfo/gtk-list
>
>
> ------------------------------
>
> End of gtk-list Digest, Vol 133, Issue 10
> *****************************************
>