Closed gnunn1 closed 7 years ago
gnunn1/tilix/issues/938 mentions 3 issues.
The deprecation message is from the import access changes introduced in 2.071. But the gtk modules publicly import the gtkc.gtktypes module so i don't think the deprecation would apply here. I'll have to check what is going on.
That change shouldn't have been in a bugfix release. gtkc.paths was deprecated in favor of a variable generated by the generator, for example for vte: https://github.com/gtkd-developers/GtkD/blob/216301209b663864f82e1254edac4b1ef08a3064/generated/vte/vtec/vte.d#L31-L36
This is the most recent change (in master), i put public imports of the new locations in the old modules. But that doesn't seem to work for fully qualified names.
3 . Fixed in master with commit 31a33cc8c85d1410f02eea478dfb75cfcc8eedbc, and that also fixes 1.
I've tagged v3.6.4 with the deprecation warning commented out, since they don't belong in a bugfix release. That should take care of 2.
Thanks Mike, works great!
various functions in GtkD are deprecated which depend on the LIBRARY methods in Loader. However, to use the alternative non-deprecated function you need to have access to the various .c modules, for example vte.c.functions but 3.6.3 does not actually generated them.
Is this a case of catching things while they are still in progress and should ignore the deprecations for now?
See issue https://github.com/gnunn1/tilix/issues/938 for examples.