Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - hanness

Pages: 1 2 [3] 4 5 ... 14
31
QB64 Discussion / Feature Request Related to the Current $Debug Work
« on: September 25, 2021, 04:36:53 pm »
When saving a program, index marks get saved so that the next time I reload the program, these index markers are available.

Likewise, it would be fantastic if breakpoints, active variable watches and variable watchpoints were saved as well. Basically, any work in progress including these debug settings would be nice to save so that they are ready to go again when the program is loaded the next time.

32
QB64 Discussion / Re: Is it possible to lock the console size?
« on: September 24, 2021, 01:35:30 pm »
Thanks. I do size the windows initially, but I shell some commands that can take 10+ minutes so it would be awkward to have to wait that long for the check of the size again.

33
QB64 Discussion / Is it possible to lock the console size?
« on: September 24, 2021, 12:48:06 pm »
I have a program that runs entirely in a console windows. All input and output happens within that console window. Is it possible to prevent a user from resizing that window? It appears that the $RESIZE:OFF metacommand does not work with the console window.

34
So far so good. Even working well with indices in my testing so far.

Can't express how freakin' awesome this is. Only wish I had all these capabilities 12,000 lines of code ago. I would probably still have hair as a result :-)

35
Thanks. That really helped me a lot.

I have a program using the console that has the ability to play back a script by simply dropping responses into the keyboard buffer.

To pause execution after some messages being displayed to the user I was running a

shell "pause"

With the script, I wanted to just effectively press ENTER when a pause command was run since we don't want pauses in the program when responses are scripted. The problem with this was that the QB64 keyboard buffer has no effect on the pause command run from shell, so execution would halt completely. Thanks to the info you provided I was able to resolve that issue and my scripts now run great.

36
I'm working on a QB64 program that uses only a console Window but it appears that Inkey$ does not function in a console window. Is there any trick that I can use to make this work?

37
Thanks!

38
I noticed that if I post a QB64 program to GitHub, GitHub indicates that the program is a FreeBasic program. Anyone know if there is a way to change this to accurately display as QB64?

I'm brand new on GitHub so I'm just now trying to figure out little stuff like this.

39
Right, but there was no response after I clarified that by "Windows Terminal" I really did indeed mean a command prompt within the "Windows Terminal" application. But that's okay. It appears that this is not possible from all that I can find.

40
Since no one is responding to my query I'll simply make the assumption that this is not possible.

41
More info about Windows Terminal can be found here:

https://docs.microsoft.com/en-us/windows/terminal/

42
My apologies. I don't think I clarified my question enough.

When I say "Windows Terminal" I am referring specifically to the "Windows Terminal" application which includes not only command console but powershell and azure shell console that can be arranged in a multi-tabbed configuration as in the image attached.

  [ You are not allowed to view this attachment ]  

43
Is it possible to have output from a QB64 program that normally goes to a console window be directed to a Windows Terminal console (CMD) window?

44
Wow, _ScreenPrint is precisely what I need. Just ran a small test program and this works great.

My plan was to grab responses from a user and save them all to a text file so that these could be played back as a script at a later without the user having to re-input all these responses again. The code to save all responses is easy, but then I would also need for every single input statement that first checked to see if there was a script file, then open the file, grab the appropriate line, stuff it into the input variable and bypass the prompt to the user since a script is present.

By simply stuffing all the previous responses into the keyboard buffer like this I won't need all that additional code.

This is brilliant!

As always, thanks for the help.

45
I have program that displays information to the user and gets input from the user entirely in a console window. There is a lot of data that gets collected from the user, requiring a good amount of typing. However, I have noticed that if I place all the responses to the program in notepad and then copy / paste to the console window, all my responses will be buffered and played back into the program from the keyboard buffer.

This has me wondering: Is there a way to inject data into the keyboard buffer from within a QB64 program?

Pages: 1 2 [3] 4 5 ... 14