AnsweredAssumed Answered

onQueryFeaturesStatusChanged signal only firing once with multiple queries

Question asked by markholm748 on Feb 11, 2020
Latest reply on Feb 20, 2020 by markholm748

I noticed that if you run multiple queries on the same layer at the same time, you only get one signal from onQueryFeaturesStatusChanged, and then you can get both results from queryFeaturesResults from the respective task ids. Is this behavior intended? I would think each query should fire the onQueryFeaturesStatusChanged signal separately.