onQueryFeaturesStatusChanged signal only firing once with multiple queries

411
2
02-11-2020 09:26 AM
MarkHolm
New Contributor II

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.

Tags (1)
0 Kudos
2 Replies
LucasDanzinger
Esri Frequent Contributor

Hey Mark,

Do you get the expected results if you use `queryFeaturesResultChanged` signal instead?

0 Kudos
MarkHolm
New Contributor II

It does, but interestingly it fixed something else at the same time. When you do 2 queries on the same features at the same time, one full and one min, the full one comes back with null attributes. This is the case when using the onQueryFeaturesStatusChanged signal.

Using the queryFeaturesResultChanged signal, this is not the case

0 Kudos