QB64 REPORT S01E02: "SCREEN modes"

[bplus]

I am just trying to show you, STx, that you don't have to makeup extra subs or functions to correct the y direction.

If you don't want to take the advice, fine, that is your business, but don't be complaining to everyone like there was no fix for y behavior readily available.

[STxAxTIC]

If there was no fix then all my graphics would be up side down. When did you ever use WINDOW in a program? Honest question. Blackjack doesn't have it, are you admitting your thinking is going upside down to accommodate the way QB64 comes by default? Say it aint so.

[STxAxTIC]

I'll admit that window might be cleaner (no pun) but i've never tested it at all, let alone with resizing and all that crap. Here is how i jump through the hoops, its pretty much one modification to each graphics statement:

Code: QB64: [Select]

1. SUB cline (x1 AS DOUBLE, y1 AS DOUBLE, x2 AS DOUBLE, y2 AS DOUBLE, col AS _UNSIGNED LONG)
2.     LINE (_WIDTH / 2 + x1, -y1 + _HEIGHT / 2)-(_WIDTH / 2 + x2, -y2 + _HEIGHT / 2), col
3. END SUB
4.  
5. SUB cpset (x1 AS DOUBLE, y1 AS DOUBLE, col AS _UNSIGNED LONG)
6.     PSET (_WIDTH / 2 + x1, -y1 + _HEIGHT / 2), col
7. END SUB

That is, you just have

Code: [Select]

x -> x + W/2
y -> -y + H/2
and the issue is over. Window may be simpler, you should test it!

[bplus]

If there was no fix then all my graphics would be up side down. When did you ever use WINDOW in a program? Honest question. Blackjack doesn't have it, are you admitting your thinking is going upside down to accommodate the way QB64 comes by default? Say it aint so.

Right! Exactly You, Stx, are the only one I know who consistently moves the origin into the center of the screen. Does calcs and then runs the x, y's through converters for screen display. So that is why I thought of you and name you, Stx, the only one I know who might really benefit from using this keyword WINDOW.

It might make your job easier and your code more understandable to others. I was offering you a gift, trying to help you as you have helped me and others often enough.

S'OK you don't have to take my advice and you don't have to be always complaining Y only goes one way in QB64 or in QB4.5 because this WINDOW command comes from there probably to get the mathematicians off the developers backs ;-))

[_vince]

It might make your job easier and your code more understandable to others. I was offering you a gift, trying to help you as you have helped me and others often enough.

Hey, let's not concede now. WINDOW is king and stx can suck it!

I'd agree that WINDOW is a bit of a toy for reasons:

Be careful with graphics commands they don't all work and there is a special command to get correct mouse location, probably can find it in Wiki under Window or related keywords.

would be a nightmare in a major project with tons of graphical routines, libraries, etc. It's at most useful in small plotting programs like OldMoses and I mentioned.

The existence of WINDOW is certainly worth acknowledging when discussing coordinate systems in regards to BASIC, though.  Only a BASIC has the balls to promise a statement that drastically changes the graphical coordinate system across the entire language.  It also means that BASIC is just as beautiful as other fancy graphing calculators like mathematica, matlab, etc when it comes to plotting because you can have a clean singular "y = sin (x)" and it will generate a legible plot.  How many hoops do you have to jump through to plot a sine wave in C?

[bplus]

Being careful for commands that don't convert, here is the extra step (see Wiki on PMAP function).

Demo focus on commands that don't convert like mouse location and _PRINTSTRING from my trig demo:

Code: QB64: [Select]

1.     '...
2.     WHILE _MOUSEINPUT: WEND
3.     mx = INT(PMAP(_MOUSEX, 2)): my = INT(PMAP(_MOUSEY, 3)) 'covert mouse to Cart Cood using PMAP
4.     '...
5.     _PRINTSTRING (PMAP(0, 0), PMAP(-1, 1)), s$
6.     _PRINTSTRING (PMAP(-95, 0), PMAP(95, 1)), "COS = x/r = " + _TRIM$(STR$(mx / r))
7.    '...
8.  

Don't know why I am so enthusiastically advocating this, it probably would be boost to my PLOT program, hmm... :) as @OldMoses has shown.

[FellippeHeitor]

Thanks to everyone who's been listening.

WINDOW was mentioned while we were preparing the episode, but I honestly forgot about the axis-flipping behavior. All that occurred to me was that we could change the origin 0,0 to another physical location on the program's screen, which is why it didn't end up being mentioned in the episode.

Thanks for the code samples, they're all really useful.

@Dav There's a track that plays in the beginning and at the end, maybe it's too faint?

Fellippe.

[Dav]

Wow, I guess I missed the music!? I really didn't notice it.  I'll listen to the next podcast without multitasking!

Will they be coming out every week?

- Dav

[bplus]

Wow, I guess I missed the music!? I really didn't notice it.  I'll listen to the next podcast without multitasking!

Will they be coming out every week?

- Dav

Yeah I was paying bills :)

I think it would be cool if Dav's music might be played, let's plug our members outside activities, Dav willing of course :) Either that or Bonkers Symphony #37 hee, hee

[TempodiBasic]

about PMAP for getting values for WINDOW settings of VIEW area of the screen

can we think this one an alternative?

Code: QB64: [Select]

1. ' p5.js Functions
2. FUNCTION map! (value!, minRange!, maxRange!, newMinRange!, newMaxRange!)
3.     map! = ((value! - minRange!) / (maxRange! - minRange!)) * (newMaxRange! - newMinRange!) + newMinRange!
4. END FUNCTION
5.  

with which the user must define from what dimensions to What Dimensions  you are calculating.
Using this function can we invert the Y (and / or the X axis) axis?

Thanks to read

[TempodiBasic]

Sorry Fellippe
Is there an youtube version also for this podcast?
I'm improving my listening but I have time to spent first to follow your discussions only by audio.  :-)
Thanks

[bplus]

about PMAP for getting values for WINDOW settings of VIEW area of the screen

can we think this one an alternative?

Code: QB64: [Select]

1. ' p5.js Functions
2. FUNCTION map! (value!, minRange!, maxRange!, newMinRange!, newMaxRange!)
3.     map! = ((value! - minRange!) / (maxRange! - minRange!)) * (newMaxRange! - newMinRange!) + newMinRange!
4. END FUNCTION
5.  

with which the user must define from what dimensions to What Dimensions  you are calculating.
Using this function can we invert the Y (and / or the X axis) axis?

Thanks to read

What's wrong with PMAP it's built in and you only have to feed it one of 4 integer arguments?

[TempodiBasic]

@bplus
Hi

What's wrong with PMAP it's built in and you only have to feed it one of 4 integer arguments?

the answer at your question is : nothing as already you know.
I was thinking about how the function of PMAP can be emulated and I remebered this function.
Good Coding

[FellippeHeitor]

Sorry Fellippe
Is there an youtube version also for this podcast?
I'm improving my listening but I have time to spent first to follow your discussions only by audio.  :-)
Thanks

Hi Tempo. Yes, there is a YouTube version, but for some reason automatic closed captions were not added this time. I don't know if I did something wrong when I uploaded it, but I ended up without them this time. I'm sorry.

If anyone knows how to trigger auto captions, please let me know.

[TempodiBasic]

@Thanks Fellippe

I'm not expert about loading video on Youtube but it seems that this time you have loaded the video with permission to edit it from the user that click on settings of Video...  when the user does this action (select Settings to activate subtitles that are disabled in this video) he has the only option to add subtitles at the place of choose the subtitle automated. And if he chooses to add subtitles he open a new window in the browser to edit the video about subtitles choosing the language and then inserting  the text or import a file with subtitles....

In the action of loading there is maybe an option to enable or not to edit subtitles... I suggest you to disable this option.
Thanks again for attempt.