On Thu, 7 Jan 2021 at 15:38, Nyall Dawson wrote:
>
> > For example, one can add all sorts of SQL-like filters to a layer
> > datasource (which was how the TimeManager plugin worked, if I understand
> > correctly) and the selection tool, vertex tool, and so on are not broken by
> > that. When so
I'm going to respond to your project-level criticism first, and then
following that I'll give a technical response:
On Thu, 7 Jan 2021 at 12:33, Cory Albrecht wrote:
>
> > and that using it for data analysis has been a secondary goal
>
>
> I'm not doing any data analysis. In fact, I doubt that
> and that using it for data analysis has been a secondary goal
I'm not doing any data analysis. In fact, I doubt that I use even 10% of
QGIS's capability.
I draw a feature that is the Kingdom of France and set the start_date and
end_date attributes appropriately (with -mm-dd resolution) a
On Tue, 5 Jan 2021 at 05:42, Cory Albrecht wrote:
>
> > 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 hear what you're saying, Nyall,
> I hear what you're saying, Nyall, I apologise if it sounded harsh, but
what do you want me to say after I find out that the latest of several bugs
has compromised my data and now I have to hunt down an unknown number of
duplicates silently created over the last few months of work? If you
empathis
> 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 hear what you're saying, Nyall, I apologise if it sounded harsh, but what
do you want me to say aft
Hi all,
Il 04/01/21 03:32, Nyall Dawson ha scritto:
> 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 --
On Sat, 2 Jan 2021 at 10:23, Cory Albrecht 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
> temp
> I understand your frustration,
Thank you.
> the usual recommendation is to use the
LTR version (currently 3.10) if you want stability, any other version
(especially master) is risky.
Using a version labelled as "release" shouldn't be risky, though. Calling
it a "release" implies that a level o
On Sat, Jan 2, 2021 at 6:34 PM Cory Albrecht wrote:
>
> > Let's try to stay positive. NTC is still young, and rapidly evolving. It is
> > hard to keep up with all (possible) use cases.
>
> I didn't say all possible use cases though. Basic tools—like identify,
> select, and the vertex editor—shou
> Let's try to stay positive. NTC is still young, and rapidly evolving. It
is hard to keep up with all (possible) use cases.
I didn't say all possible use cases though. Basic tools—like identify,
select, and the vertex editor—should not break when one adds a new feature
as they are commonly used t
On 1/2/21 1:17 AM, Cory Albrecht 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 controll
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 v
13 matches
Mail list logo
