I still had to manually go get a library from ncurses to get FB 1.0 to work on my version of 64 bit Linux. It was something like libtinfo.so.5 That's interesting! I'm using 32-but Linux (Ubuntu 14.04, previously Ubuntu 12.04), and the solutions given in this thread worked for me. I have no clue why...

Maybe we could add a feature to Inkey that prevents it hogging the CPU by limiting the number of times it can be called per second. It could keep an internal counter, and if it exceeds a certain value it could sleep a short while if the counter was started within the last second, and then reset the...

dkl wrote:Write "__getkey" (two underscores prefix) instead of "getkey":

Code: Select all

#lang "qb"
print __getkey

Thanks so much. It worked perfectly! No CPU usage wasted while waiting in input loops!

:-)

Okay, then I will switch to Getkey.

The man page on it says that it's only available in -lang qb (which I'm using) if it's "referenced with the alias __Getkey".

I've never referenced anything with an alias before - what is the code to do this?

Thanks!

Hi all, I'm running the current version of FBC (1.01.0) on a x32 Linux system under Ubuntu. Pentium 4 processor, 2.8 GHz. When my FB programs are waiting for user input (i.e. DO: LOOP UNTIL INKEY$ = ...), the CPU usage is near 100%. This causes my processor to heat up and the fan to speed up in resp...

Adapting it for #lang "qb", I think it would have to be: #lang "qb" __extern __fb_enable_vt100_escapes alias "__fb_enable_vt100_escapes" as long dim shared __fb_enable_vt100_escapes as long __fb_enable_vt100_escapes = 0 That's it!! :-) I put that at the beginning of my...

Okay, so I downloaded and installed the new build that incorporates the changes you made. I added the line "__fb_enable_vt100_escapes = 0" at the beginning of my program, and compiled it using the regular "fbc -lang qb foo.bas" command line. The program is still sending across th...

dkl wrote: ... you can also ... use one of the daily builds provided by St_W.

Okay, excellent. Thank you so much, dkl! This is true community support!

Okay, thank you for making this work for me! :-)

How do I use that take that hinit.c code and apply it to the copy of FreeBASIC on my computer? Or will it be included in the next release?

dkl wrote:On the other hand, for *BSD systems, FB does assume a start position of 1,1 already (and does not query the cursor position in any way).

Okay, so is that a functionality you can add - either via a command-line switch or "lazy initialization" - to the Linux form of FB?

"\e(U" INIT_CHARSET inits PC 437 characters set "\e(B" EXIT_CHARSET exits PC 437 characters set Those are afaik not vt100, but only for emulations of it by PCs. Thus not standarized Correct. Let's note, though, that the *ACTUAL* VT100 standard as published in 1978 doesn't includ...

However, the real issue for now are the hard-coded sequences. Does the termcap/terminfo data base contain these sequences? I could not find anything related to querying cursor position on termcap/terminfo manpages. (notice also the "(not in termcap)" comments from FB source code) Wow, I n...

Bump. Using debug-monitor mode on my terminal, this is what I figured out: FB is not properly using Curses or Ncurses. Evidently, FB has some hard-coded VT100 escape sequences in it, because it's sending those ALONG WITH actual Wyse 60 escape sequences. My terminal is a Wyse 60, and Linux recognizes...

TJF wrote:It shouldn't be a problem to handle serial communication in a thread. Have a look at function family KeyPgThreadcreate.

It says threading isn't allowed in -lang qb dialect, which is what I'm using in my program.

Any other options for this?

Thanks!

I'm writing a POS (cash register) program for a friend of mine who runs a small convenience store. I want the POS to be able to control the gas pumps. The interface for the gas pumps hooks to the computer via a serial port, and constantly sends and receives data (pump authorization request, pre-pay ...