Idea, detections are hidden when behind a custom mask

[Tinbum1]

At the moment the program still logs detection's in the mask history even if they are hidden behind a custom mask. Might it be a good idea that these are not stored making it easier to go through the relevant dynamic mask detail history and also reducing the size of the json file. It may also reduce processing time? or perhaps not.

[Tinbum1]

Also on the Dynamic mask Detail tab/ active masks, when you click on a mask it shows the mask on the image with a description of what it is. Would it be possible to add the 'key' so the mask can be easily identified.

[VorlonCD]

Sure, look for it in the next update

[Tinbum1]

Thank you.

[VorlonCD]

Back to your original suggestion, not storing masked items (and potentially false detection) may save some time loading the database but I cant say how much. You would sacrifice the ability to troubleshoot detection's. The latest version is faster, do you think it is worth creation an option for it?

[Tinbum1]

Yes, option is great idea. It would help reduce the masks in the Dynamic mask history and active page. I'm getting dynamic masks created for items hidden behind custom masks.

[VorlonCD]

Right now the dynamic mask routine is run BEFORE the check if something is masked with the old style image mask. Perhaps it should be the other way around?

[Tinbum1]

That sounds logical to swap it.

[VorlonCD]

these features working for you ok?

[Tinbum1]

Yes brilliant , thank you.

This program is just getting better and better all the time. Thank you for all your hard work and incorporating all our suggested features and the ones your coming up with.