>Is based in your path
 Tip Your Landlord Shirt $21.68 |
 DMT Has Friends For Me Shirt $21.68 |
Tip Your Landlord Shirt $21.68 |
>Is based in your path
>Is based in your path
Tip Your Landlord Shirt $21.68 |
DMT Has Friends For Me Shirt $21.68 |
Tip Your Landlord Shirt $21.68 |
quite based in a way
still, should be more modular, more portable, and less NIH syndrome QString
the C++ stdlib is such a flaming pile of wieners that at this point i just assume there's a valid reason whenever qt reinvents something
>the C++ stdlib is such a flaming pile of wieners that at this point i just assume there's a valid reason whenever qt reinvents something
wrong, there is no reason for most of their Q
Just say it: you like having flaming wieners up your ass.
>and less NIH syndrome QString
Much of the functionality of Qt predates C++ standardization. It's not NIH syndrome if nobody has invented it and published it yet.
actually it's slop that's much worse than win32.
Win32 is the standard windowing API on linux thanks to Wine/Proton
Idk, I made an in house tool for work that gave me some leeway to frick around with Qt and I had a pretty easy time just overriding nativeEvent in my QMainWindow subclass. The real answer is to just bite the bullet and implement your own QStyle so everything on Windows doesn't look like it's from 2007 (not in the good way, either).
like what, you mean it's not fruit tiger awewo?
zoom zoom
I ignored him because he's wrong
>Win32 is the standard windowing API on linux thanks to Wine/Proton
This is interesting. How true is this?
Can I use something like VS from 2009 but with C#?
Yeah, literally anything you write as a Winforms program will run on Linux out of the box on all distros with no tweaks.
It is the best way to make a GUI on linux.
kek
the absolute state
To be fair, modern Windows GUI development is just as shitty as freetard GUIs.
Win32 is love, Win32 is life.
if you're talking about running full-blown Visual Studio on Linux, that might be painful since the editor is pretty tightly coupled to the NT Kernel IIRC.
I mean using vs 2009 to develop applications for linux (and windows). I would have to use it on linux as well. I remember using the wysywig with visual basic for win32 in college was actually fun
I wish QWidgets got as much love as the QML shit, bros...
they're going all-in on qml especially now that you can compile it to native code, old style qt will stick around for some time because it's used for a lot of embedded use-cases but it would not surprise me if they abandon it at some point within the next decade once qml-to-native is in good shape.
>it's used for a lot of embedded use-cases but it would not surprise me if they abandon it at some point within the next decade
Those use cases are usually quite happy to pay for support and aren't going to be interested in rewriting all their shit into QML. They've got medical devices, industrial plant controllers, and all sorts of stuff like that to sell!
Based until you encounter QTableView
>Based until you encounter QTableView
what about it?
anyway isn't tree view harder
i don't quite remember well (it was in 2018 after all) but it involved me at work, launching a prototype for application for a mining company in a week, and being stuck for a solid 3 days implementing a table with checkboxes inside it. up until then qt5 was pretty smooth sailing them BAM a huge uphill in difficulty
i think i had to deal with QAbstractItemModel as
said
Why the hell would you code a windows GUI in C? Lol, just use WPF.
implementing a model is easy. Implementing the pain() function is way too much work for something so fricking simple. Gtk got it right define widgets and factory classes so it can be reused not this painter bullshit that introduces a additional logic barrier and fricks with styling.
Worst of all you cannot make these things in the designer its astonishing how shit qt designer is for non standard stuff.
Fricking tell me about it. I ended up just inheriting from QAbstractItemModel and then writing some general purpose delegates when I was pulling my hair out trying to work with a tree view like
said.
when are they going to support modules I hate writing header files. Not even the macro only version works via modules.
its nice but i still have a hard time understanding the more complex things
I like PySide
Me 2, bud.
Proprietary product with tinker troon alternative licence
Is it me or Qt is extremely bloated, even small applications have noticeable delay on startup. Is GTK any better i that regard?
It's just you lil sis
>sepples monstrosity
>requires its own compiler
No.
its own compile
I use gcc / clang
what are you talking about 'tard
look up MOC
although im pretty sure it isn't used for signals/slots anymore since c++11... or is it? i have no idea tbh i only used qt once and thought it was cool but then electron appeared and thats the gui toolkit everyone uses now
>but then electron appeared and thats the gui toolkit everyone uses now
*only homosexuals
you can just use macros instead. moc just auto generates code its not a compiler.
>im pretty sure it isn't used for signals/slots anymore since c++11... or is it?
Certainly seemed to be in the code I was writing last week.
As long as you follow a few simple rules (use cmake, put class definitions in header files, use Q_OBJECT at the top of classes that have signals or slots) it Just Works. The moc (and related tools) is faster than your C++ compiler by several orders of magnitude.
uh why do you Black folk know about these libraries? My exposure is literally oh I need this library for the app I want? Ok I'll install it