Problem whith PCOPY

[Cobalt]

Hey just look at our avatar choices! ;-))

*counts colors in Bplus avatar*
1... 2... 3... 4... .... ....?

Yep need those 16m colors!

[bplus]

*counts colors in Bplus avatar*
1... 2... 3... 4... .... ....?

Yep need those 16m colors!

Yep need those shades! QB4.5 red and blue and that god awful green wouldn't do!

And don't let Pete get you with "Lay off the weed and learn to read!"

That's a Trump trick to cast dispersion's on others so people don't see how severely handicapped he is with Screen 0.

BTW I tried to count colors in your avatar, ha! Ha!

[SMcNeill]

But not sure how to get the colors from screen 0 to translate back in a 32 bit screen mode.

Look in the SaveImage library.  It shows how to convert a text screen to a graphical screen.  (And then it saves it to a picture, which you can just LOADIMAGE and use, if you want to change resolutions, or not.)

Quick run down of the process:
USE SCREEN(), POINT (), or _MEMIMAGE to get the color and character of each block on the text screen.
Create a graphic screen of WIDTH * _FONTWIDTH, HEIGHT * _FONTHEIGHT size
Now just set foreground, background color and PRINT each character, in place, on your graphical screen.

[Cobalt]

Quick run down of the process:
USE SCREEN(), POINT (), or _MEMIMAGE to get the color and character of each block on the text screen.
Create a graphic screen of WIDTH * _FONTWIDTH, HEIGHT * _FONTHEIGHT size
Now just set foreground, background color and PRINT each character, in place, on your graphical screen.

I kind of meant with the PEEK method where it just returns 0-255 for the color value. And even simpler, Screen 0 having a base of 0-15 colors.

[SMcNeill]

I kind of meant with the PEEK method where it just returns 0-255 for the color value. And even simpler, Screen 0 having a base of 0-15 colors.

It still returns a value from 0 to 255.  4 bits are foreground color, 3 bits are background, and the last bit toggles blinking on and off.  You’ll need to MOD and \ your return value to get the colors used.  ;)

[Pete]

Hey everybody, cover your eyes. Pete's FLASHING again!

Code: QB64: [Select]

1. _CONTROLCHR OFF
2. SCREEN 0, 0, 0, 0
3. DO
4.     COLOR 7, 0: CLS
5.     x0$ = "": x1$ = ""
6.     f = f + 1: IF f > 30 THEN b = b + 1: f = 0
7.     IF b > 15 THEN IF f = 30 THEN EXIT DO ELSE b = 0
8.     COLOR 7, 0: PRINT "f ="; f, "b ="; b;
9.     COLOR f, b
10.     LOCATE 1, 40: PRINT "Pete..."
11.     FOR i = 1 TO 47
12.         x0$ = x0$ + CHR$(SCREEN(1, i))
13.         x1$ = x1$ + CHR$(SCREEN(1, i, 1))
14.     NEXT
15.     PCOPY 0, 1
16.     SLEEP
17.     COLOR 7, 0: CLS
18.     SLEEP
19.     PCOPY 1, 0
20.     LOCATE 2, 1
21.     FOR i = 1 TO 47
22.         IF ASC(MID$(x1$, i, 1)) \ 16 >= 8 THEN
23.             ' Flashing
24.             'PRINT ASC(MID$(x1$, i, 1)) MOD 16 + 16, ASC(MID$(x1$, i, 1)) \ 16 - 8
25.             COLOR ASC(MID$(x1$, i, 1)) MOD 16 + 16, ASC(MID$(x1$, i, 1)) \ 16 - 8
26.         ELSE
27.             ' Non-Flashing
28.             COLOR ASC(MID$(x1$, i, 1)) MOD 16, ASC(MID$(x1$, i, 1)) \ 16
29.         END IF
30.         PRINT MID$(x0$, i, 1);
31.     NEXT
32.     COLOR 7, 0
33.     SLEEP
34. LOOP
35.  

Just to prove there is a way in SCREEN 0 to differentiate flashing from non-flashing characters. I apologize in advance if I'm off on any of the color parameters. I didn't want to spend much time on this, so I didn't check it for accuracy. It's just to demonstrate the method I'd use to detect flashing colors on the screen, and preserve them, which PCOPY will not do on its own.

Just hold a key down to "flash" through all the color combos. When f > 15 "Pete..." will flash. The second line "Pete..." will flash as well, which is possible only because of the conditional color algorithm. Let me know if it needs any tweaking or if anything was missed. I may have actually made something like this 20+ years ago for a screen saver routine.

Pete

[Cobalt]

It still returns a value from 0 to 255.  4 bits are foreground color, 3 bits are background, and the last bit toggles blinking on and off.  You’ll need to MOD and \ your return value to get the colors used.  ;)

But no way to directly translate the base(foreground) color to 32bit mode.
which seems odd since we can ,sort of, use 32bit colors in screen 0
COLOR _RGB(255,0,0)

least I believe _RGB() finds the nearest color in the available palette. But we cant reverse the process, presumably cause 32bit modes have no palette to compare from. However QB45 did have a base palette to work with, so maybe we could add that under the hood and pull the RGB values off of that internal palette?

It would make it easier to translate old QB45 code to QB64 if someone wanted to make use of a larger screen but didn't want to have to rewrite everything. Just change the SCREEN line but not have to worry about going through the code and changing all the COLOR statements. Yes probably a nitch scenario.
An augmentation of the COLOR statement, if used in 32bit mode to automatically choose from the palette if a value 0-255 is used?

[SMcNeill]

But no way to directly translate the base(foreground) color to 32bit mode.
which seems odd since we can ,sort of, use 32bit colors in screen 0
COLOR _RGB(255,0,0)

least I believe _RGB() finds the nearest color in the available palette. But we cant reverse the process, presumably cause 32bit modes have no palette to compare from. However QB45 did have a base palette to work with, so maybe we could add that under the hood and pull the RGB values off of that internal palette?

It would make it easier to translate old QB45 code to QB64 if someone wanted to make use of a larger screen but didn't want to have to rewrite everything. Just change the SCREEN line but not have to worry about going through the code and changing all the COLOR statements. Yes probably a nitch scenario.
An augmentation of the COLOR statement, if used in 32bit mode to automatically choose from the palette if a value 0-255 is used?

Use _RED, _GREEN, _BLUE.

For example, SCREEN 0 High Intensity Blue might be 125, 125, 255.  (I don’t remember the exact values, but you can get them with the command.)

Then use _RGB32() with those values to convert to a 32-bit color . 

[SMcNeill]

Quick demo:

SCREEN 0
FOR i = 0 TO 15
    PRINT I, _RED(I), _GREEN(I), _BLUE(I)
NEXT

[Cobalt]

Hey everybody, cover your eyes. Pete's FLASHING again!

Code: QB64: [Select]

1. _CONTROLCHR OFF
2. SCREEN 0, 0, 0, 0
3. DO
4.     COLOR 7, 0: CLS
5.     x0$ = "": x1$ = ""
6.     f = f + 1: IF f > 30 THEN b = b + 1: f = 0
7.     IF b > 15 THEN IF f = 30 THEN EXIT DO ELSE b = 0
8.     COLOR 7, 0: PRINT "f ="; f, "b ="; b;
9.     COLOR f, b
10.     LOCATE 1, 40: PRINT "Pete..."
11.     FOR i = 1 TO 47
12.         x0$ = x0$ + CHR$(SCREEN(1, i))
13.         x1$ = x1$ + CHR$(SCREEN(1, i, 1))
14.     NEXT
15.     PCOPY 0, 1
16.     SLEEP
17.     COLOR 7, 0: CLS
18.     SLEEP
19.     PCOPY 1, 0
20.     LOCATE 2, 1
21.     FOR i = 1 TO 47
22.         IF ASC(MID$(x1$, i, 1)) \ 16 >= 8 THEN
23.             ' Flashing
24.             'PRINT ASC(MID$(x1$, i, 1)) MOD 16 + 16, ASC(MID$(x1$, i, 1)) \ 16 - 8
25.             COLOR ASC(MID$(x1$, i, 1)) MOD 16 + 16, ASC(MID$(x1$, i, 1)) \ 16 - 8
26.         ELSE
27.             ' Non-Flashing
28.             COLOR ASC(MID$(x1$, i, 1)) MOD 16, ASC(MID$(x1$, i, 1)) \ 16
29.         END IF
30.         PRINT MID$(x0$, i, 1);
31.     NEXT
32.     COLOR 7, 0
33.     SLEEP
34. LOOP
35.  

Just to prove there is a way in SCREEN 0 to differentiate flashing from non-flashing characters. I apologize in advance if I'm off on any of the color parameters. I didn't want to spend much time on this, so I didn't check it for accuracy. It's just to demonstrate the method I'd use to detect flashing colors on the screen, and preserve them, which PCOPY will not do on its own.

Just hold a key down to "flash" through all the color combos. When f > 15 "Pete..." will flash. The second line "Pete..." will flash as well, which is possible only because of the conditional color algorithm. Let me know if it needs any tweaking or if anything was missed. I may have actually made something like this 20+ years ago for a screen saver routine.

Pete

Now Modify your program to make use of a Dark Grey in the background. Surely with your mighty Screen 0 knowledge you can.

[Pete]

Code: QB64: [Select]

1. OUT &H3C8, 0
2. OUT &H3C9, 10
3. OUT &H3C9, 10
4. OUT &H3C9, 10
5. msg$ = "Cobalt's Sofa Kingdom :D"
6. COLOR 15, 0: PRINT msg$
7. SLEEP

Pete

[SMcNeill]

When Pete says he likes to do things the hard way, he’s not kidding.

Why use something slow and hard to decipher, like: ASC(MID$(x1$, i, 1))

You know, you can just use ASC(x1$, i), and accomplish the exact same thing...

If there’s ever a need for an obsolete, overly-complicated solution to a simple problem, Pete’s the guy to go to, to ask for advice on it!

[Cobalt]

Code: QB64: [Select]

1. OUT &H3C8, 0
2. OUT &H3C9, 10
3. OUT &H3C9, 10
4. OUT &H3C9, 10
5. msg$ = "Cobalt's Sofa Kingdom :D"
6. COLOR 15, 0: PRINT msg$
7. SLEEP

Pete

Something tells me your method there wont produce these results.

[Pete]

Code: QB64: [Select]

1. PALETTE 7, 56
2. msg$ = "Bright white text on a dark grey background, on a black screen..."
3. COLOR 15, 7: PRINT msg$
4. SLEEP