A quick look at the doc file shows PTR_GEN called first. IIRC it introduces a new CONsole driver which I guess History links into - I may be wrong.
Implement command history
-
- Over Heated PSU
- Posts: 136
- Joined: Tue Nov 30, 2021 1:19 am
Re: Implement command history
Re: Implement command history
Ok, thanks (I struggled reading the docs)ones' complement wrote: ↑Wed Mar 13, 2024 4:10 pmA quick look at the doc file shows PTR_GEN called first. IIRC it introduces a new CONsole driver which I guess History links into - I may be wrong.
Will give it a miss as I'm not into the PE currently, maybe it's a project for me to work on
Many thanks
-
- Over Heated PSU
- Posts: 136
- Joined: Tue Nov 30, 2021 1:19 am
Re: Implement command history
You don't really need to know anything to use PTR_GEN (just LRESPR it to make it resident). The only difference you'll probably see is it manages a jobs (aka program) windows, when you switch between jobs it neatly deals with restoring/saving screen contents.
Re: Implement command history
Ok, will take a look thanksones' complement wrote: ↑Wed Mar 13, 2024 4:18 pm You don't really need to know anything to use PTR_GEN (just LRESPR it to make it resident). The only difference you'll probably see is it manages a jobs (aka program) windows, when you switch between jobs it neatly deals with restoring/saving screen contents.
Re: Implement command history
Just tried it on Q-emuLator successfully so will give it a go on QL later
Many thanks
Many thanks
Re: Implement command history
Works great on the real QL, thanksones' complement wrote: ↑Wed Mar 13, 2024 4:18 pm You don't really need to know anything to use PTR_GEN (just LRESPR it to make it resident). The only difference you'll probably see is it manages a jobs (aka program) windows, when you switch between jobs it neatly deals with restoring/saving screen contents.
Was concerned ptr_gen might eat a lot of resources but doesn’t seem to
Many thanks