[Bug ?!] _RGB32 issue with CONST

[TempodiBasic]

Hi guys
while I'm trying to code with QB64 version 1.3 96937f0  I have got this issue....

I can affirm that _RGBA32 and CONST are good friends and code works fine  but it is not the same about CONST and _RGB32

well CPR (copy->paste->run) this code

Code: QB64: [Select]

1. CONST YVel = 5, Hscreen = 400, Wscreen = 600, Rball = 10, MaxBall = 10
2. CONST Blu = _RGB32(0, 0, 255), Green = _RGB32(0, 255, 0)
3. DIM Yball(1 TO MaxBall) AS INTEGER, A AS LONG, W AS INTEGER, CountBall AS INTEGER
4. DIM K AS STRING
5. A = _NEWIMAGE(Wscreen, Hscreen, 32)
6. IF A < -2 THEN SCREEN A ELSE PRINT "Error in Screen setup"
7.  
8.  
9. DO
10.     K = INKEY$
11.     CLS
12.     LOCATE 1, 1: PRINT " press Space to shoot, Esc to quit      Countball="; CountBall
13.     PRINT " to test the issue press space while balls arrive to the top of screen"
14.     FOR W = 1 TO MaxBall STEP 1
15.         IF Yball(W) > 0 THEN
16.             CIRCLE (400, Yball(W)), Rball, Blu
17.             PAINT STEP(0, 0), Blu, Blu
18.             LINE (200 - 1, Yball(W) - 1)-STEP(Rball + 2, Rball + 2), Green, B
19.             LINE (200, Yball(W))-STEP(Rball, Rball), Blu, BF
20.  
21.             Yball(W) = Yball(W) - YVel
22.             IF Yball(W) <= 0 THEN IF CountBall > 0 THEN CountBall = CountBall - 1
23.         END IF
24.     NEXT W
25.     IF K = " " THEN
26.         IF CountBall < MaxBall THEN
27.             CountBall = CountBall + 1
28.             Yball(CountBall) = (Hscreen - (2 * Rball))
29.         END IF
30.     END IF
31.     _LIMIT 10
32. LOOP UNTIL K = CHR$(27)
33. END
34.  

works fine Yes!

now please CPR this one code

Code: QB64: [Select]

1. CONST YVel = 5, Hscreen = 400, Wscreen = 600, Rball = 10, MaxBall = 10
2. CONST Blu = _RGB32(0, 0, 255)
3. CONST Green = _RGB32(0, 255, 0)
4. DIM Yball(1 TO MaxBall) AS INTEGER, A AS LONG, W AS INTEGER, CountBall AS INTEGER
5. DIM K AS STRING
6. A = _NEWIMAGE(Wscreen, Hscreen, 32)
7. IF A < -2 THEN SCREEN A ELSE PRINT "Error in Screen setup"
8.  
9.  
10. DO
11.     K = INKEY$
12.     CLS
13.     LOCATE 1, 1: PRINT " press Space to shoot, Esc to quit      Countball="; CountBall
14.     PRINT " to test the issue press space while balls arrive to the top of screen"
15.     FOR W = 1 TO MaxBall STEP 1
16.         IF Yball(W) > 0 THEN
17.             CIRCLE (400, Yball(W)), Rball, Blu
18.             PAINT STEP(0, 0), Blu, Blu
19.             LINE (200 - 1, Yball(W) - 1)-STEP(Rball + 2, Rball + 2), Green, B
20.             LINE (200, Yball(W))-STEP(Rball, Rball), Blu, BF
21.  
22.             Yball(W) = Yball(W) - YVel
23.             IF Yball(W) <= 0 THEN IF CountBall > 0 THEN CountBall = CountBall - 1
24.         END IF
25.     NEXT W
26.     IF K = " " THEN
27.         IF CountBall < MaxBall THEN
28.             CountBall = CountBall + 1
29.             Yball(CountBall) = (Hscreen - (2 * Rball))
30.         END IF
31.     END IF
32.     _LIMIT 10
33. LOOP UNTIL K = CHR$(27)
34. END
35.  

and you can see the issue...
_RGB32 need a own single row of code to work with CONST
see attachment to sum of issue
  [ You are not allowed to view this attachment ]  
Thanks to read and try.

[bplus]

That's funny, for me, no blue in first:

Code: QB64: [Select]

1. CONST Blu = _RGB32(0, 0, 255), Green = _RGB32(0, 255, 0)

and the 2nd works fine:

Code: QB64: [Select]

1. CONST Blu = _RGB32(0, 0, 255)
2. CONST Green = _RGB32(0, 255, 0)
3.  

Probably because you need one variable per CONST:

Code: QB64: [Select]

1. CONST Blu = _RGB32(0, 0, 255): CONST Green = _RGB32(0, 255, 0)  'works
2.  

Append: Looked up CONST. And I guess you should be able to do more than one on a line with just a comma.

[Cobalt]

has to due with the ALPHA option in _RGB32
if you do this it will work

CONST Blu = _RGB32(0, 0, 255, 255), Green = _RGB32(0, 255, 0, 255)

in QB64 v1.1 it wasn't necessary to fill all 4 options out so it must have to due with one of the tweaks done to the _RBG\_RGB32 routines for V1.3

[TempodiBasic]

Hi Bplus
sorry for this necromancy but I fall today in this experience....

about your right suggestion

Probably because you need one variable per CONST:
Code: QB64 [Select]
CONST Blu = _RGB32(0, 0, 255): CONST Green = _RGB32(0, 255, 0)  'works

well it seems that the issue comes back as warning "Invalid name on current line "if we use three definitions on the same line of code!
copy and paste in your QB64Ide this code to see

Code: QB64: [Select]

1. CONST CPlanet = _RGBA32(238, 111, 89, 255): CONST CMoon = _RGBA32(100, 227, 11, 255): CONST CBlack = _RGBA32(0, 0, 10, 255)
2.  

and with this my zombie I say you good coding this is just a feedback.
Thanks to read

[bplus]

And yet this works!

Code: QB64: [Select]

1. CONST CPlanet = _RGBA32(238, 111, 89, 255), CMoon = _RGBA32(100, 227, 11, 155), CBlack = _RGBA32(0, 0, 50, 255)
2. SCREEN _NEWIMAGE(800, 600, 32)
3. CIRCLE (100, 100), 30, CPlanet
4. CIRCLE (200, 200), 10, CMoon
5. CIRCLE (300, 200), 105, CBlack
6.  

[TempodiBasic]

Great this one experience!

now it works also old error!  :D I cannot believe!
I have done no adjournment about QB64 or Windows 10 and I'd got this news

please copy and paste...

Code: QB64: [Select]

1. 'CONST CoPlanet = _RGBA32(238, 111, 89, 255): CONST CoMoon = _RGBA32(100, 227, 11, 255): CONST CoBlack = _RGBA32(0, 0, 10, 255)
2. CONST CoPlanet = _RGBA32(238, 111, 89, 255): CONST CoMoon = _RGBA32(100, 227, 11, 255), CoBlack = _RGBA32(0, 0, 10, 255)
3.  
4. CONST CPlanet = _RGB32(238, 111, 89, 255), CMoon = _RGB32(100, 227, 11, 155), CBlack = _RGB32(100, 0, 50, 255)
5. SCREEN _NEWIMAGE(800, 600, 32)
6. CIRCLE (100, 100), 30, CPlanet
7. CIRCLE (200, 200), 10, CMoon
8. CIRCLE (300, 200), 105, CBlack
9.  

now also _RGB32 works fine just with the comma separator!
Thanks for reply.

[Raven_Singularity]

Why would three CONST separated by colons ":" be any different than having three CONST on different lines?

I always thought ":" was equivalent to a new line.

[SMcNeill]

Why woul three CONST separated by colons ":" be any different than having three CONST on different lines?

I always thought ":" was equivalent to a new line.

CONST is an internal replacement type routine, and with the colon parsing, it’s a little buggy with self referential calls on the same line.

CONST x = 3: CONST y = x

The above line of code will probably glitch out on you, as QB64 tries to process it.  The x = 3 should register a CONST value of x, but it doesn’t update those definitions until it gets to the end of the line, so the second segment will see y = x as being an undefined variable reference.

If colons were handled as separate lines, we wouldn’t see this glitch, but they’re not.  They’re more indicators of segmenting a line of code into multiple commands.  Think of the following:

x = 3: y = 4: PRUNT x + y

Whoooops!!  I misspelled PRINT!  Which LINE is that code on, when the error pops up at the bottom line of the IDE?

It’s on line 1, not line 3. 

*************************

Generally speaking, CONST should work without any glitches in relation to colons, but it current doesn’t.  Since it’s generally an easy work around (just separate the lines), and I’ve been occupied with other things in life, it hasn’t been a high priority fix on my list of things to do.

Turn

CONST x = 3: CONST y = x

into:

CONST x = 3
CONST y = x

And the glitch should go away, when it presents itself.

[Raven_Singularity]

^ Thanks for the detailed explanation.  Fascinating.  I can see the issue with line numbering now.