Re: Glib::Threads:Private

On 20/02/2019 15:26, Paul Davis wrote: On Wed, Feb 20, 2019 at 1:17 AM John Emmas > wrote: I realise it's a deprecated interface but can anyone explain what Glib::Threads:Private does? [...] It means that each thread that accesses the

[gtk-osx-users] cannot build core libraries

hi, im right now with my second clean mojave installation, and i follow the instruction on this site: https://wiki.gnome.org/action/show/Projects/GTK/OSX/Building?action=show=Projects%2FGTK%2B%2FOSX%2FBuilding i could again build all except: meta-gtk-osx-core and meta-gtk-osx-gtk3 on

Re:

*hijacks the thread further* On Thu, 21 Feb, 2019 at 6:36 AM, Igor Korot via gtk-list wrote: What I do argue is why the context-menu event should care what mouse button click it comes from? Yah, it's a bit odd there isn't a high-level context-menu signal for widgets. Given it's important

Re:

On Wed, Feb 20, 2019 at 12:36 PM Igor Korot wrote: > > This is all correct and I'm not arguing about that. > > What I do argue is why the context-menu event should care what mouse > button click it comes from? > if the menu is shown on button press (not release) (and this is typical), then

Re:

Paul, On Wed, Feb 20, 2019 at 12:30 PM Paul Davis wrote: > > > > On Wed, Feb 20, 2019 at 11:10 AM Igor Korot wrote: >> >> Hi, Paul, >> >> On Wed, Feb 20, 2019 at 12:03 PM Paul Davis >> wrote: >> > >> > >> > >> > On Wed, Feb 20, 2019 at 10:49 AM Igor Korot via gtk-list >> > wrote: >> >> >>

Re:

On Wed, Feb 20, 2019 at 11:10 AM Igor Korot wrote: > Hi, Paul, > > On Wed, Feb 20, 2019 at 12:03 PM Paul Davis > wrote: > > > > > > > > On Wed, Feb 20, 2019 at 10:49 AM Igor Korot via gtk-list < > gtk-list@gnome.org> wrote: > >> > >> > >> Why do we even talking about button number, when the doc

Re:

On Wed, Feb 20, 2019 at 12:10 PM Igor Korot wrote: > > Hi, Paul, > > On Wed, Feb 20, 2019 at 12:03 PM Paul Davis > wrote: > > > > > > > > On Wed, Feb 20, 2019 at 10:49 AM Igor Korot via gtk-list > > wrote: > >> > >> > >> Why do we even talking about button number, when the doc explicitly said

Re:

Hi, Paul, On Wed, Feb 20, 2019 at 12:03 PM Paul Davis wrote: > > > > On Wed, Feb 20, 2019 at 10:49 AM Igor Korot via gtk-list > wrote: >> >> >> Why do we even talking about button number, when the doc explicitly said >> "right-click", which implies "right mouse button". > > > X Window (at the

Re:

On Wed, Feb 20, 2019 at 10:49 AM Igor Korot via gtk-list wrote: > > Why do we even talking about button number, when the doc explicitly said > "right-click", which implies "right mouse button". > X Window (at the very least) allows buttons to be remapped. Button #1 is typically the left mouse

Re:

On Wed, 2019-02-20 at 11:49 -0600, Igor Korot wrote: > I know I am kind of switching the topic here, but... > > Why do we even talking about button number, when the doc explicitly > said > "right-click", which implies "right mouse button". Yes, I noticed that contradiction myself when answering

Re:

Hi, Stefan et al, On Wed, Feb 20, 2019 at 11:33 AM Stefan Salewski wrote: > > On Wed, 2019-02-20 at 11:07 -0600, Igor Korot via gtk-list wrote: > > Hi, ALL, > > This link https://developer.gnome.org/gtk3/stable/GtkToolbar.html#Gtk > > Toolbar-popup-context-menu > > states that the parameter

Re:

On Wed, 2019-02-20 at 11:07 -0600, Igor Korot via gtk-list wrote: > Hi, ALL, > This link https://developer.gnome.org/gtk3/stable/GtkToolbar.html#Gtk > Toolbar-popup-context-menu > states that the parameter "button" can be "-1". > > What is the scenario when this occurs, i.e. it should be the

Re:

Nevermind. Didn't read the whole description. Sorry for the noise. Thank you. On Wed, Feb 20, 2019 at 11:07 AM Igor Korot wrote: > > Hi, ALL, > This link > https://developer.gnome.org/gtk3/stable/GtkToolbar.html#GtkToolbar-popup-context-menu > states that the parameter "button" can be "-1". >

[no subject]

Hi, ALL, This link https://developer.gnome.org/gtk3/stable/GtkToolbar.html#GtkToolbar-popup-context-menu states that the parameter "button" can be "-1". What is the scenario when this occurs, i.e. it should be the button number that was clicked IIUC? Thank you for clarification.

Re: Glib::Threads:Private

On Wed, Feb 20, 2019 at 1:17 AM John Emmas wrote: > I realise it's a deprecated interface but can anyone explain what > Glib::Threads:Private does? > > Does it guarantee that 'SomeObject' can only be accessed by code running > in a particular thread? And if so, does it do that by creating a >

Glib::Threads:Private

I realise it's a deprecated interface but can anyone explain what Glib::Threads:Private does? Does it guarantee that 'SomeObject' can only be accessed by code running in a particular thread? And if so, does it do that by creating a specific thread for the object - or does it use whichever