Abs error? - Socoder

-=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- (c) WidthPadding Industries 1987 0\|511\|0 -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=-
Socoder -> Blitz -> Abs error?
Sat, 12 Mar 2022, 08:00
spinal	Abs error? With 3 arrays like following... Dim maskR(336,336) Dim maskG(336,336) Dim maskB(336,336) --v The following code gives an "Operator can not be applied to stings" error on the If Abs(maskB(x,y)-b) < 100 Then --v line. No idea why LockBuffer BackBuffer For y = 0 To 336 For x = 0 To 336 argb = ReadPixelFast(x,y) r = (argb Shr 16) And 255 g = (argb Shr 8) And 255 b = argb And 255 If Abs(maskR(x,y)-r) < 100 Then If Abs(maskG(x,y)-g) < 100 Then If Abs(maskB(x,y)-b) < 100 Then argb = (255 Shl 24) Or (255 Shl 16) Or (0 Shl 8) Or (255) WritePixelFast(x,y,argb) End If End If End If Next Next UnlockBuffer --v -=-=- Check out my excellent homepage!
Sat, 12 Mar 2022, 09:19
Jayenkai	What an odd error! Have you tried forcing them to be numbers with the .. um.. I want to say % sign? Dim maskR%(...) I think. tries .. Oddly, I'm not getting the error. -=-=- ''Load, Next List!''
Sat, 12 Mar 2022, 09:28
spinal	Turns out I dont need to check the g and b values for what I want, but.... it is very odd. Maybe its a memory problem? -=-=- Check out my excellent homepage!
Sat, 12 Mar 2022, 09:29
Jayenkai	Are you still using that "Not Mark's coding" version of Blitz? -=-=- ''Load, Next List!''
Sat, 12 Mar 2022, 10:07
spinal	This one... -=-=- Check out my excellent homepage!
Sat, 12 Mar 2022, 10:19
Jayenkai	Hmm.. that's mine. shrugs Maybe something else, somewhere in the code. Who knows... -=-=- ''Load, Next List!''
Sat, 12 Mar 2022, 10:37
spinal	Graphics 800,600,0,2 settingcolour = 0 SetBuffer BackBuffer() ; crop to 336x336 ; from 62,10 ; 194 images imageStrip = CreateImage(sWidth, sHeight) tempImage = CreateImage(336,336) myAnim = LoadImage("C:\Users\Spinal\Desktop\brains\tile000.png") ; test mask = LoadImage("C:\Users\Spinal\Desktop\brains\tile157.png") ; image to compare all others to outimg = CreateImage(336,336) Dim maskR%(336,336) Dim maskG%(336,336) Dim maskB%(336,336) LockBuffer BackBuffer For y = 0 To frameHeight For x = 0 To frameWidth argb = ReadPixelFast(x,y) maskR(x,y) = (argb Shr 16) And 255 maskG(x,y) = (argb Shr 8) And 255 maskB(x,y) = argb And 255 Next Next UnlockBuffer a$ = "C:\Users\Spinal\Desktop\brains\tile" c$ = ".png" f = 0 SetBuffer BackBuffer() While f < 194 b$ = f If Len(b$) = 1 Then b$ = "0"+b$ If Len(b$) = 2 Then b$ = "0"+b$ file$ = a$+b$+c$ outfile$ = "C:\Users\Spinal\Desktop\brains\nobg\frame"+b$+".png" myAnim = LoadImage(file$) DrawBlock myAnim,0,0 f = f + 1 LockBuffer BackBuffer For y = 0 To 336 For x = 0 To 336 argb = ReadPixelFast(x,y) r = (argb Shr 16) And 255 g = (argb Shr 8) And 255 b = argb And 255 If Abs(maskR(x,y)-r) < 90 Then ;If Abs(maskG(x,y)-g) < 120 Then ;If Abs(maskB%(x,y)-b) < 100 Then argb = (255 Shl 24) Or (255 Shl 16) Or (0 Shl 8) Or (255) WritePixelFast(x,y,argb) ;End If ;End If End If Next Next UnlockBuffer GrabImage(outimg,0,0) SaveImage(outimg,outfile$) Flip(1) ;Delay(100) If KeyHit(1) Then End Wend While Not KeyHit(1) Delay 1 Wend End --v -=-=- Check out my excellent homepage!
Sat, 12 Mar 2022, 10:59
Jayenkai	It's the b variable. b$=f <--- Then later you use b for blue. -=-=- ''Load, Next List!''
Sat, 12 Mar 2022, 11:05
spinal	Dammit Why couldn't blitz tell the difference between b and b$... gggrrrrrr -=-=- Check out my excellent homepage!
Sat, 12 Mar 2022, 14:04
Dan	Its a bit odd, yes, but only if you come to blitz basic from other languages, which do make such distinctions. On the other hand, if you see it on the brighter side: You are defining the variable either as string, int or float - ONCE, and then later you do not need to use the that extra char. (yes the readability/debugabilitiy is maybe not so well, but ...) test$="Hi" Print test WaitKey() --v I think that is better than to have the variables defined and to be forced to use the same definiton in the code later ... see: test:int=100 for test:int= 1 to 10 print test:int next test:int --v