- This topic has 49 replies, 1 voice, and was last updated 8 months ago by
.
-
Posts
-
-
> Create gtk application
> Decide to port it to gtk4
> Half of the toolkit was deprecated
> Text rendering is shit now
> Important features gone, can’t do basic stuff
> GtkHeaderBar now has layout problems
> No obvious way to set GtkHeaderBar child spacing anymore> no gtk_main, no gtk_main_quit
g_signal_connect(win, "destroy", G_CALLBACK(gtk_main_quit), NULL);
gtk_main();is now
static bool done = false;
void quit(GtkWidget *widget, gpointer data) { done = true; }g_signal_connect(win, "destroy", G_CALLBACK(quit), NULL);
while (!done) g_main_context_iteration(NULL, TRUE);> Barely capable of creating a ui anymore
lmao what is this shit?
-
woke af gnome devs amarite
-
that what’s you deserves when you decides to use Gimped ToolKit
-
it’s a new toolkit, adapt your app to lateat standardsor keep the outdated design. It’s not like it will stop working
-
Already found a bug, where clicking a header-bar-button and another window steals focus, locks the button in active state forever
Using GTK_DEBUG=interactive to check why the header-bar layout is broken crashed the inspector twice…
-
>Already found a bug
you’ve already reported it too, right anon? right? -
>Already found a bug
It isn’t a bug. It’s a feature. #CLOSED #WONTFIX -
the ABSOLUTE STATE of gscrotes
-
-
Just use libagar
-
>no gtk_main, no gtk_main_quit
Having control over your own event loop is good, stop whining-
You had the same control before, they just removed convenient functions
-
-
> Create gtk application
Stopped reading there. Only idiots do that. -
Why do you feel the need to port to gtk4?
It adds nothing substantial but to break everything that’s working like last time.
It’s the habit of gtk devs, you should have learnt that. I don’t blame them because that’s how they are. So, it’s totally your fault for adopting a unstable new version. -
> Important features gone, can’t do basic stuff
What basic stuff can you not do?
> GtkHeaderBar now has layout problems
Example?
>no gtk_main, no gtk_main_quit
Deprecated since GTK3. GTK3 has been out for a decade.
>static bool done = false;
void quit(GtkWidget *widget, gpointer data) { done = true; }>g_signal_connect(win, "destroy", G_CALLBACK(quit), NULL);
while (!done) g_main_context_iteration(NULL, TRUE);
Don’t use C, it’s verbose.-
As far as I know, the custom title widget MUST now be centered correctly. Before, there was a way to have it expand left and right, but now the title buttons will cause massive padding.
> inb4 it’s a feature
-
Isn’t the headerbar able to contain multiple items? Just add a box and go from there.
-
-
-
Take the win32 pill and make your program windows exclusive
-
https://i.imgur.com/ilO9Gnr.gif
Found another feature
-
Move to Qt. There’s no point in arguing with GNOMEtards or jumping through hoops to use their broken ass software.
-
Nobody who shills Qt on the internet actually uses it.
Notice how they always conveniently fail to mention that it literally needs its own separate compiler.-
I both use and program in qt. It’s amazing.
Moc isn’t a compiler, it generates c++ code containing plumbing to make signals/slots on your new classes work. You could write that code yourself like the g_tards, but why would you? -
a lot of nonfree shitware is Qt. At work the main toolkit on the screens are Qt4. It’s shit though, I’d rather it was GTK. There are better GTK bindings in langs other than C/C++ as well, imo.
-
>they always conveniently fail to mention that it literally needs its own separate compiler
I find it interesting that you conveniently failed to mention this misterious separate compiler.
Shithead.
-
-
>static bool done = false;
void quit(GtkWidget *widget, gpointer data) { done = true; }g_signal_connect(win, "destroy", G_CALLBACK(quit), NULL);
while (!done) g_main_context_iteration(NULL, TRUE);you are supposed to use gtkapplication and gtkapplicationwindow
> Barely capable of creating a ui anymore
I think you are just scrotebrained.-
I will not use dconf to store data
I will not use gtk to parse my command line arguments
I will not use their dumb org.organization.software convention as my application name (An assertion will fail if I don’t do it that way)
I just want to show a window with buttons, images and labels.Why can’t it just be like gtk2?
-
Fuck you
-
>I will not use their dumb org.organization.software convention as my application name (An assertion will fail if I don’t do it that way)
The ultimate brainlet moment. Oh wait, it’s LULZ, I forgot. -
>I will not use dconf to store data
whats stopping you from not using it?
>I will not use gtk to parse my command line arguments
pretty sure gtk4 does not parse command line arguments anymore. argv passed to gtkapplication is parsed you just modify that.
>I just want to show a window with buttons, images and labels.
and you still can? What is your problem here? As far as I have seen gtk4 seems easier. But then again I have more experience with pyqt than with gtk.
>Why can’t it just be like gtk2?
well the devs are poopyholes if you want it to be more gtk2 like you need to contribute
-
-
-
Just use gtk2
-
Gtk2 doesn’t even support portals, so you are forever stuck with the shitty gtk file picker.
-
-
>Decide to create gtk application
>Grab all the latest shit on tumbleweed
>Open up Gnome Builder since you wanna get the full experience
>Takes 10 minutes to prepare the project, apparently its gotta download a whole other bunch of shit to even work
>Eventually get the Hello World window to pop up
>"Ok now I’d better like add another control of something"
>Try opening up the ui file in their gui builder
>Get a nag screen basically saying "Nope! your GTK is too recent you can’t use this shit"
>End up throwing computer out of windowBravo Gnome devs, bravo!
-
>>Try opening up the ui file in their gui builder
gtk 4 isn’t supported by glade. Wait for the new gui builder that is on their gitlab called drafting works alright will be incorporated into the builder. Anyway gnome builder is a piece of shit and only works with flatpak shit don’t use it. Its a lot easier to use a normal text editor and follow the elementary os guide.-
See this is the kind of shit problem that permeates this platform. The integrated stuff the evangelists go on about turns out to be a half-baked piece of shit and you end up having to go back to the 90’s to develop anything real on it. By which point, why even bother when you can have a much better experience developing on other platforms?
-
what other platforms are there without any/less problems? Qt has their own set of issues while their IDE is quite nice most people don’t want to work with c++. Lazarus is a hidden gem dragged down by pascal.
-
Other platforms aren’t perfect but at least you can build something with them before running into problems. And they usually have better quality docs which get straight to the point with good examples.
I’d take qt creator and c++ over gtk and gnome builder any day. Lazarus is pretty cool apart from the pascal thing, the IDE quickly becoming a mess of hidden windows, and the compile times being strangely slow compared to Dephi from the 90’s.
-
if your only problem with gtk so far was the ui builder then that is apperntaly going to be fixed in gnome 42 once they integrate the new ui builder which is works with gtk3 and 4 and is much nicer to use.
I agree the lack of examples for gtk in the docs are terrible but the tests usually serve as good example on how to use the library.
I find the qt docs to be much worse since its so bloated and you can’t find a damn thing without reading the whole page as a beginner.
-
-
-
-
> Its a lot easier to use a normal text editor and follow the elementary os guide.
Dios mio. So this is the power of FOSS? Can’t even have a proper ide to work and actually build stuff?
-
-
-
i thought gtk4 was meant to be gtk3 stable
-
What’s the point of throwing in the trash an entire codebase every few years?
What about the software that was made in previous versions and is now "deprecated"?-
You can use Lazarus and its components to build a GUI interface just like you would in visual studio, just dragging and dropping buttons on the screen. The library used by Lazarus also compiles to windows and macos besides Linux.
It uses gtk2, gtk3, qt4 or qt5 on Linux. You can pick whatever you want.I’d take qt creator and c++ over gtk and gnome builder any day. Lazarus is pretty cool apart from the pascal thing, the IDE quickly becoming a mess of hidden windows, and the compile times being strangely slow compared to Dephi from the 90’s.
The compile time is slower than delphi because it’s not the same compiler. Lazarus uses Free Pascal compiler which is pretty good but just not as fast as Delphi.
You can use docked windows on Lazarus now, using a third part package. The team is adding it as an out of the box option for the IDE too, which will be a godsend when it finally arrives.
I like Pascal. It’s a lot like C# in many things.-
How is creating custom components in lazarus? Is it easy to handle higher level os-level keyboard events (for composition, editing states, copy & paste, etc)?
-
Creating components is easy. You can actually use OOP in Pascal because it’s easy to read.
There’s plenty of events in place for handing key pressing, drag and dropping stuff, etc. You just double click them in the IDE and Lazarus creates a procedure for handling it.
-
-
-
-
>lmao what is this shit?
GTK is not meant to be used, you have been memed -
>2004+17
>still no file picker thumbnails-
Just as LULZnome intended.
-
-
come home
-
>kdenlive
low tier troll
-
-
Tech advances sweaty. if you want the latest futures on the latest hardware I’m afraid you’ll have to use the latest tools 🙂
-
https://gitlab.gnome.org/GNOME/gtk/-/issues/583
>Maximize window
>Move mouse cursor to top-right corner
>Click mouse button to close the window
>Window does not close
Many such cases!-
Some applications in windows are like that, and when I close them I acidentally close something important that was behind. I HATE THAT
-
-
- You must be logged in to reply to this topic.