Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
bug when using _Dest _Console
#21
https://qb64phoenix.com/forum/showthread...69#pid6669

If the function detects a newline is it changed only to CHR$(13)? On Windows might have to do CHR$(13) + CHR$(10) instead, if the intention was to produce a new line. But what is it with that funny space that keeps being shown in these screenshots? Now I understand that the "qbs_input()" is allocating a space to put in something else. It appears in many other places in the code. Confusing but it's how Galleon originally designed it to emulate M$QB string management.
Reply
#22
I was able to use ctrl+c to copy from the console, and ctrl + v to paste to input. The right click might be something Indy is recalling form some pop-up menu QBasic had. I rarely used that, and for the life of me, I can't recall when and where it was available. The sheel window, maybe?

Oh well, like Mark stated, now CONSOLE has 3 things going for it.

Pete
Shoot first and shoot people who ask questions, later.
Reply
#23
Quote:I looked at the screenshot. "scanf()" only picks up as many characters as it thinks should fit into the type asked for by the "format" first parameter it's given, that's why it displayed strange values in the first and second attempts. If it's going to convert improperly like that, it's not going to matter if it could accept 10 digits or 100 digits.


Yes, but it shows that something is wrong. And that, I think, is the main thing. 

"scanf" is one of those things, but I'd have to look at my books and notes again now -- No, nullo interresto!  Rolleyes
Reply
#24
(09-14-2022, 07:07 PM)bplus Wrote: Oh yeah, you can copy paste from console, just not from right mouse menu:

A menu won't appear on right-click but it does copy the contents of your selection.

[Image: image.png]
Tread on those who tread on you

Reply
#25
https://github.com/QB64Official/qb64/issues/33

This is very interesting. Maybe not for folks using Windows.

BTW that other QB64 does the same exact thing @Jack observed.
Reply
#26
(09-16-2022, 08:45 PM)mnrvovrfc Wrote: https://github.com/QB64Official/qb64/issues/33

This is very interesting. Maybe not for folks using Windows.

BTW that other QB64 does the same exact thing @Jack observed.

Similar issues with $CONSOLE:ONLY with my Win10, but I'm using Development build 2.1 still.

Pete
Reply
#27
Have y'all considered using the console input functions
Tread on those who tread on you

Reply
#28
(09-20-2022, 04:11 PM)Spriggsy Wrote: Have y'all considered using the console input functions

Since when did Indiana cross the Mason-Dixon line?

Pete Big Grin
Reply




Users browsing this thread: 8 Guest(s)