Jump to content
  • Sky
  • Blueberry
  • Slate
  • Blackcurrant
  • Watermelon
  • Strawberry
  • Orange
  • Banana
  • Apple
  • Emerald
  • Chocolate
  • Charcoal
LordJashin

OSI TPA Function testing

Recommended Posts

Freddy was pretty fast in finding that the TPAExtractTriangle function wasn't working right? That or I missed something...owell.

 

Anyway here is the new Divi/TPAfunctions.scar file. You would have to download the latest OSI to run it, with the latest SCAR that has the TPAExtractTriangle fix if you wanted to see the triangle xD. Or change the include at the top of the file to just {$I OSI/OSI.scar}...

 

Here are the results of the test file (pretty nifty :P):

 

ITzJ5.gif

 

About: THE RED DOTS and Boxes are TPointArrays (an array of Points e.g. x, y coordinate)! This shows them Visually!

 

Left is before the TPA related function ran. And right is after.

 

 

 

Been looking at some SRL threads. FindTPointCluster, and some other functions look interesting. I'm going to finish the testing on color finding, and other finding methods before going after that though...

 

EDIT: Didn't know this. Try right clicking Image or Input area inside the Target client panel in SCAR. There's an edit button O_O

Edited by LordJashin

Share this post


Link to post
Share on other sites

Thanks for that and fixing the trianglez :)

 

Forgot to mention. The part on that animated image of the TPA functions that ISN'T labeled. Is the part where I used SwapTPA. To swap the x's and y's on all the points...threw SwapTPA in there just to see how it would come out.

 

I need to do all of this stuff I have planned then go full out on the making of tutorials. I could have a bunch with just referring to the test files as examples. Need to knock the basics out though more in that beginners tut...

Share this post


Link to post
Share on other sites

Interesting stuff. I wish I could give more useful input but just not enough time. Have you browsed through/played around with everything in Debug.scar?

Share this post


Link to post
Share on other sites

Yes, and I opted to not use those functions because I wanted something static. I don't like how the colors change each time when debugging TPA's, and etc. I might just update those functions to make them more customizable, but the problem is, they already have a ton of params to begin with...

Share this post


Link to post
Share on other sites
Yes, and I opted to not use those functions because I wanted something static. I don't like how the colors change each time when debugging TPA's, and etc. I might just update those functions to make them more customizable, but the problem is, they already have a ton of params to begin with...

 

Haha yea nah there just there to fulfill the needs of the above average user nothing to do with 1000 customizable options when those people should just create their own debugging functions for that purpose such as you did.

 

I just wanted to see what you thought, and I guess you answered my question already.

 

You'd have quite an appreciation for a lot of things in OSI after using the ones in SRL for so many years.

Share this post


Link to post
Share on other sites
Lol, how much slower is the ones in SRL?

 

Speed is negligible. Just less efficient coding, I don't care for the end product much, and the parameters are annoying and limited.

Share this post


Link to post
Share on other sites

Agreed, and i would choose longer descriptive named functions over smaller confusing names any day. Like RAstAToPoint or something. Some of the functions just laugh at. Look at them, then look at SCAR's. A bunch do the same things, but their names. :D lols

 

params can be confusing as well sometimes...

Share this post


Link to post
Share on other sites
Agreed, and i would choose longer descriptive named functions over smaller confusing names any day. Like RAstAToPoint or something. Some of the functions just laugh at. Look at them, then look at SCAR's. A bunch do the same things, but their names. :D lols

 

params can be confusing as well sometimes...

 

Name is negligible. I'm more concerned with why they don't utilize type parameters like TBox etc. plus it's just limited not being able to do things like DebugTBA(TBoxArray) etc.

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

×