SRL Archive - Development

(Planned features)

Per point:

• Colour
• Tolerance
• SearchAreaSize (previously areasize)
• AreaBlockSize: The given area must all be the given colour. (Like areasize but all points must match)
• AreaBlockSizeCount / Percentage: amount of points to match colour
• BadPoint: Must match or not match.

Per whole dtm:

• Amount of points to match?

i like them. :)

Rotated DTMs pl0x :)

How about making it return the colors that did not match? That way we could check if they are yellow/red (npc/drop dot). Would be great!

If only a DTM was an object..

From: lordsaturn
If only a DTM was an object..

Why on earth would you want it to be an object? :)
It's a datastructure. I don't see the use of making it a class, except for the fact that it would be more easy to modify. Making it a class is IMO really a weird idea… Would probably slow it down a bit too, as well as hogging more memory.

I guess the memory part isn't a real issue. But why would you want it to be an object?

From: Markus
Rotated DTMs pl0x :)

Rotated has been added some time ago.

Do we still want the extra features? Perhaps they're a bit overkill.

They are nice, but I feel like they aren't really necessary, and would cause it to slow down.

Can't hurt, unless from an efficiency standpoint as nava2 mentioned.

Areablocksize count has an actual use (detecting walls @ mm) so I'd say go for that one if you feel like doing it. Of course they aren't really necessary but it never hurts.

From: Nava2
They are nice, but I feel like they aren't really necessary, and would cause it to slow down.

Granted I know nothing about DTMs or this particular code, but adding more functions/procedures shouldn't have any effect on the speed of anything else.

From: moparisthebest
Granted I know nothing about DTMs or this particular code, but adding more functions/procedures shouldn't have any effect on the speed of anything else.

In this case it is functionality rather than functions, do more checks etc in a normal FindDTM(). :)

From: Wizzup?
In this case it is functionality rather than functions, do more checks etc in a normal FindDTM(). :)

If it's going to significantly slow down anything, either make an option (like an extra parameter) or make a new FindDTMWithSomeOtherCoolOption()? :)

Or just ignore me. :spot:

AreaBlockSizeCount / Percentage: amount of points to match colour

This would be really nifty to have, I've been in serveral situations where I really could've used a feature like this.

OK. It'll be a bit complicated to add but surely not impossible I think. ;)