[QGIS-Developer] Temporal controller issues

[Nyall Dawson]

On Sat, 2 Jan 2021 at 10:23, Cory Albrecht <maps at hanfastolfe.com> wrote:
>
> Can somebody help me under the basics of how things work inside QGIS starting from when it loads all the features for a layer through the steps, and then finally drawing them on the map canvas, specifically with respect to the new temporal controller (NTC)?
>
> The issues caused by the NTC have been very frustrating for me as I make mostly (historical) timeline maps and I relied heavily on the old TimeManager (OTM) plugin by Antia Graser and group. So many tasks are now much more laborious or difficult because so many tools are just not time-aware.
>
> Was it not possible to add the NTC in such a way that would have still let all the other features work as before with the filtered feature set before being made time-aware, rather than confusingly operating on the unfiltered set? Or perhaps it shouldn't have been turned on until the infrastructure was there for the tools to be time-aware right away?
>
> Because I've just submitted yet another bug about the NTC, this time for the selection tool, and it has me more than a little annoyed. As a result of this bug I now have an unknown number of duplicate objects in multiple layers across multiple databases/projects that I unknowingly pasted into them over the past several months since the NTC was added to QGIS.
>
> I feel that the NTC was both poorly thought out and badly implemented as all these bugs would indicate.

I can empathise with your frustration, but this is a very complex discussion!

As background, I implemented time handling for vector layers as a
VOLUNTEER (completely unpaid). Would you have preferred I didn't do
this, and we had no time support for vectors at all? Please be very
wary of your language in future -- every piece of feedback worded like
this directly equates to a developer losing interest in volunteering
their time on QGIS, to the harm of all.

I've fixed two of your issues here
https://github.com/qgis/QGIS/pull/40834, as an UNPAID VOLUNTEER.
Without funding I'm just not interested in fixing the snapping related
issues. I don't personally have any need for these, and the QGIS
snapping code isn't something I'm motivated in getting involved with
at all. Perhaps there's another developer interested in looking at
this, or perhaps a developer will take a look at this during the 3.18
bug sprint. Or maybe someone will pay for this fix and financial gain
will be the motivation.

I like making the world a better place through volunteering my time on
making a first-class desktop mapping application, but I'm far from
being a slave to this, and my family, garden, and drum kit want my
time too!

Nyall



> _______________________________________________
> QGIS-Developer mailing list
> QGIS-Developer at lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer