×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Hello Rob,
Am 08.07.2020 um 13:20 schrieb Rob Berendt <rob@xxxxxxxxx>:
I am curious as to whether or not this screen was waiting on input. Most people use EXEFMT to display screens. This is because they write some stuff out, then read some input from the user.
You nailed it. That's the main problem. If your application is waiting for response from the user, there can no write happen, for two reasons:
- The program is in DSPW and waits for input to read, when the user presses enter,
- The program is stuck at READ and can't continue other tasks, so it's useless anyway to be able to do a write. With what?
A possible use case for my question would be a chat program, like
https://en.wikipedia.org/wiki/Talk_(software) but line-oriented instead of character based. Maybe the data queue approach mentioned by [error, can't find the message anymore] with two programs or threads might be a possible solution? One for the sending side, one for the receiver, to put received messages into the queue, to be displayed as soon as they arrive, hopefully *without* erasing what the user began to type?
I guess I'll need to check this out with a proof of concept program.
:wq! PoC
PGP-Key: DDD3 4ABF 6413 38DE -
https://www.pocnet.net/poc-key.asc
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
