Re: Cross platform development

On 03/18/2017 04:03 PM, Michael Torrie wrote: > On 03/18/2017 07:37 AM, Dirk Gottschalk via gtk-app-devel-list wrote: >> The only chance is, to grab the DLLs from MinGW via objdump ore some >> similar, like recommended and pack them into the applications working >> directory, because Windows

Re: Cross platform development

On 03/18/2017 11:25 AM, Lucas Levrel via gtk-app-devel-list wrote: > Le 17 mars 2017, à 23:02, Dirk Gottschalk via gtk-app-devel-list a écrit : > >> I'm developing a multi platform application with GTK+ for Windows and >> Linux. >> >> >> IIRC is GTK+ and it's dependencies not linkable statically,

Re: Cross platform development

On 03/18/2017 08:07 AM, pelzflorian (Florian Pelz) wrote: > gedit deploys msys2 but removes a bunch of files it does not need. This > way, the binary will end up in a bin/ directory though. Of course you > can make a link or a bat script for launching it in the main directory. &

Re: Cross platform development

On 03/18/2017 04:07 AM, Michael Torrie wrote: > I think some programs stick their binary and libraries in a bin folder, > and GTK can still find it's files. It's more typical for windows apps > to put the EXE in the toplevel folder though. > gedit deploys msys2 but removes a bunch of files it

Re: gtk+-3.10.4 bundle and gtk+3.6 or what bundle for application 1 -10

On 11/22/2016 12:04 AM, songqing shan wrote: > Hi, > > > I would like to have anyone to help me. > > > I use MinGW+msys and gtk+-3.10.4 bundle to compile examples on the >

Re: Getting focus

I believe shell integration is the only clean way to do a Wayland-compatible guake. Am I wrong? ___ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list

Fwd: Re: accessor functions in gtk3

This too. Forwarded Message Subject: Re: accessor functions in gtk3 Date: Thu, 30 Jun 2016 14:38:49 -0700 From: Herminio Hernandez Jr <herminio.hernande...@gmail.com> To: pelzflorian (Florian Pelz) <pelzflor...@pelzflorian.de> On 06/30, pelzflorian (Florian Pelz) wr

Fwd: Re: accessor functions in gtk3

This apparently should have been sent to the list. Forwarded Message Subject: Re: accessor functions in gtk3 Date: Thu, 30 Jun 2016 22:30:10 +0200 From: Nicolas Soubeiran To: pelzflor...@pelzflorian.de Hi, If I don't know about the im context (I

Re: accessor functions in gtk3

On 06/30/2016 07:25 AM, Herminio Hernandez Jr wrote: > The error I got was that 'im_context' was no a member of the struct GtkEntry. > I believe the accessor function that I should use is > gtk_entry_im_context_filter_keypress (). However I am having a hard time > trying to figure out how to

Re: disabling mouse scroll on GtkComboBox and spin buttons

On 05/22/2016 11:54 AM, jcup...@gmail.com wrote: > x = gtk_combo_box_new_text(); > g_signal_connect(x, "scroll-event", G_CALLBACK(true_cb), NULL); > ... Ah yes, this is a much better way. ___ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org

Re: disabling mouse scroll on GtkComboBox and spin buttons

On 05/22/2016 08:36 AM, Lokesh Chakka wrote: > Hello, > > Is there a way to disable mouse scroll on GtkComboBox and GtkSpinButton > widgets ? > > an example will help much. > > Thanks & Regards > Use a function like static void disable_scroll (GtkWidget *widget) { GdkEventMask events;

Re: Compiling for Windows [Was: argv revisited]

On 05/06/2016 07:01 PM, Lucas Levrel wrote: > Le 5 mai 2016, Andrew Robinson a écrit : >> 1) Because there are between 40 to 120Mb worth of libraries or their >> dependencies I would have to post on my website. > > It's not clear to me whether one has to distribute GTK if it's linked >

Re: Compiling for Windows [Was: argv revisited]

On 05/04/2016 03:59 PM, Andrew Robinson wrote: > No, there are no Win32 binaries in MSYS2. Where are you getting your > information? > MSYS2 contains pacman. `pacman -Syu mingw-w64-x86_64-gtk3` downloads GTK+ binaries for x86_64 and puts them in the C:\msys64\mingw64 directory (by default). This

Re: Compiling for Windows [Was: argv revisited]

On 05/04/2016 02:22 AM, Andrew Robinson wrote: > I have an idea! Why doesn't someone just compile all the binaries for Win32 > and Win64 and make them available on the Internet, that way none of us will > have to go through all this stupid BS just to get some binaries? Just two > packages, one for

Re: Compiling for Windows [Was: argv revisited]

On 05/03/2016 08:34 PM, Dov Grobgeld wrote: > The complete gtk run time is only about 20MB in size (at least for gtk2) > which with todays hard disk sizes really is negligable, so I agree that > there is no reason to try to create a common gtk runtime. > > I still remember the frustration back in

Re: Compiling for Windows [Was: argv revisited]

On 05/03/2016 06:12 PM, Dave Howorth wrote: > On 2016-05-03 16:57, Florian Pelz wrote: >> I'd like to have one standard GTK+ installer for the GTK+ DLLs etc. that >> can be downloaded and installed from other installers, so there is just >> one GTK+ installed on Window

Re: Compiling for Windows [Was: argv revisited]

On 05/03/2016 04:57 PM, Andrew Robinson wrote: > Well I can't ship MSYS2 and MXE with my application, and I most certainly > can't sell any application to grandma and grandpa, if it requires instructions > on how to install MSYS2 and MXE just so you can run my application. > For MSYS2, you

Re: Compiling for Windows [Was: argv revisited]

On 05/02/2016 12:36 PM, Lucas Levrel wrote: > […] > > I'm not an expert programmer and when I wanted to compile for Windows > the software I developped in Linux, I couldn't achieve a satisfactory > result (using the -mwin32 or -mwindows flag gave either a clumsy > additional command window, or

Re: Suggestion for text editing module

On 04/18/2016 04:43 PM, Matthew A. Postiff wrote: > Thank you for this suggestion. It might work. We are not doing WYSIWIG > because our focus is on the text. Someday it would be nice to add a > third view like print layout but for now we just have (1) text view and > (2)

Re: Suggestion for text editing module

On 04/17/2016 02:04 PM, Matthew A. Postiff wrote: > Hi, > > I have a gtk2 app that is, among other things, an editor for a data > format called USFM. The program can display the data (text) in the > encoded format, or in a pretty format, and the user can edit the data in > either view. The editor

Re: argv

On 04/16/2016 07:59 PM, Andrew Robinson wrote: > Don't forget that GTK is already running on top of the Windows command line > and therefore I have no direct access to it. Everything is processed by GTK > before I can ever get to it for myself. > > I do suspect that Windows may be the cause of

Re: argv

On 04/16/2016 06:50 PM, Andrew Robinson wrote: > Assembly language has no calling convention whatsoever until you hand code it > to have whatever calling convention you want it to have, preferably matching > the calling convention of whatever you are interfacing to. > This is not a matter of

Re: argv

On 04/16/2016 06:23 PM, Andrew Robinson wrote: > That is completely incorrect. By definition, main(argc,argv) means that before > you add even one line of code, argc and argv are on the stack, ready to be > used. That's how it should be in C, but not necessarily in assemblers. Since you seem to

Re: argv

On 04/16/2016 10:53 AM, Lucas Levrel wrote: > Gtk2 came with "gtk-demo". Doesn't Gtk3 have a similar app? However, I > don't know if it parses command-line args, if that's what you're looking > for. > It is called gtk3-demo and it doesn't parse command-line args because its examples are not run

Re: argv

GTK+ has no influence on the command line until you call gtk_init on it, after which a valid command line remains a valid command line. Your problem is not related to GTK+. What influences the command line is the way GoLink calls main, so you should be asking your question on the GoDev forum.

Re: argv

On 04/15/2016 09:59 PM, Andrew Robinson wrote: > I may be the only person writing a > program in GoAsm for for GTK+3 and cross-OS, but that has nothing to do with > my problem. That you use GoAsm and GoLink instead of GCC can make a difference. Different build toolchains may not be compatible.

Re: argv

On 04/15/2016 09:30 PM, Mark Cianfaglione wrote: > […] > To the community's defense I have to say that I've never seen anyone use > ANY Gtk from assembler in the 7+ years that I've been using it. (Other > than what is compiled from GCC.) > > Sounds like you are breaking new ground. Do keep the

Re: argv

On 04/12/2016 01:58 PM, David Marceau wrote: > If you really need to resort to assembler, just run the gcc/g++ compiler > with the "-c -S" to generate the assembler to see how they gcc compiler > does it with the above gtkhello.c This here really is good advice. If you don't want to read GNU