On Windows, afaik IUNknown is stdcall. So this probably never has been used on windows.
Are you cross compiling or trying to build a gtk3 windows app ?
Davo
why do you need gtk in windows?Whereas it it usually recommended to use the default look for the OS, it can be the case that one wants to have the same look across all platforms. (E.g. games, sometimes corporate, etc)
why do you need gtk in windows?Whereas it it usually recommended to use the default look for the OS, it can be the case that one wants to have the same look across all platforms. (E.g. games, sometimes corporate, etc)
This is not uncommon.
It would be enough to remove the calling conventions from the implementation. It's correct in the interface part of TGtk3Widget. Probably using Code Completion let to the addition of only the cdecl in the implementation.One could use winapi instead of a specific convention, since that chooses the right calling convention for a platform and works not just on windows. Assumes 3.2.0 or higher.
Apparently it is, if this is the first time it is compiled on Windows :-) The GTK3 port is half a decade old.I never used GTK3, but there are many GTK2 applications available on Windows for the reasons I mentioned.
It would be enough to remove the calling conventions from the implementation. It's correct in the interface part of TGtk3Widget. Probably using Code Completion let to the addition of only the cdecl in the implementation.One could use winapi instead of a specific convention, since that chooses the right calling convention for a platform and works not just on windows. Assumes 3.2.0 or higher.
Apparently it is, if this is the first time it is compiled on Windows :-) The GTK3 port is half a decade old.I never used GTK3, but there are many GTK2 applications available on Windows for the reasons I mentioned.
The point I try to make is not related to GTK3, but to any portable widgetset.
Most of those applications have gtk on Windows because they are hardcoded to GTK and thus are condemned to it. It is not a choice but a result of the lack of choice.So we agree? ;D
Apparently it is, if this is the first time it is compiled on Windows :-) The GTK3 port is half a decade old.I never used GTK3, but there are many GTK2 applications available on Windows for the reasons I mentioned.
(isn't Blender one of those? and how about the mingw interface? Just to name two)
I put that in the same category as "wow, someone is going to ride a push bike across the Simpson Desert" ! It may be possible but why on earth would you do it ?
If the folks at CT are so hot with GTK3, I cannot but think their efforts would be more useful focusing on Unix platforms where GTK is a lot more comfortable !
(Honestly, I thought Gnome had given up with its 'portable' model with GTK2, but here it is, how to setup GTK3 on Windows, gee !
https://www.gtk.org/docs/installations/windows/
The page even has a real Windows look and feel. )
Davo
....
B) Beyond completing it on non-Windows platforms, they also made it work properly (as it should) on Windows.
...
OK, are you saying that CT has working GTK3 on, eg, Linux ? Now, that would impress me, I missed your hint completely !
Sir
CodeTyphon has already GTK3 support for projects.
.....
Thats very interesting.
This -
https://www.pilotlogic.com/sitejoom/index.php/88-wiki/technical/400-what-is-platform.html
and this -
https://www.pilotlogic.com/sitejoom/index.php/forum/general-discussions/5402-gtk3.htmlQuoteSir
CodeTyphon has already GTK3 support for projects.
.....
Seems to be the only relevent mention of GTK3 on their entire website.
The first link is quite confusing, the second supports what you say in a very understated way. Further research is indicated !
Davo
So, as Akira1364 said, a full import anyone ? :-[ :-[How big diff does it make? IIRC CodeTyphon has no public revision control system. If the diff is very big, it must be split into manageable and testable pieces.
I would go as far as to suggest there would be no downside to simply copying and pasting the entire CodeTyphon version of the GTK3 LCL
Yep, I have to agree, CT appears to be doing GTK3 better than Lazarus. Someone has been very busy, what a pity they have not pushed those improvements back to Lazarus where they started from !I see it pretty tough, given the attitude of the codetyphon developers.
Yep, I have to agree, CT appears to be doing GTK3 better than Lazarus.Please give an example where the CT version works better. I didn't test CT now much. Actually I was not able to install it as normal user. Installing as root caused some hassle later.
OK, I have done a few test between a week old Lazarus, a day old Lazarus and Lazarus 2.2.0 and, of course CT.Oh, if LCL-GTK3 is worse in the development branch "main", then we must find which revision caused it.
First of all, you are not going to be pleased to hear this, some things work better in Lazarus 2.2.0 that all the rest, specifically the bitmaps that appear in Speedbuttons, its correct in 2.2.0, rubbish is all the rest.
I do not see any improvements delivered by your merge (but I am testing on Linux so getting rid of the writeln's is obviously a good thing for Windows).Yes, the commit was 02115d373b794b3, "LCL-GTK3: Turn WriteLn into DebugLn. Make sure they compile. Cleanup."