dilwyn wrote: ↑Sun Mar 17, 2024 9:19 pm The problem lies with the QLiberator QJ extension for listing jobs. It works in SBASIC, listing the jobs correctly (I'm using QLib 3.45a).
I presume that the code for jobs is the same as in v2. 11, and that one works. So the quickest workaround would be to compile with an older version of Qliberator, maybe v3. 36
In the end it was easier to change to using JOBS than to reinstall an older version of QLib.
Largely untested Launchpad v2.14 update attached, just the files which have changed (Launchpad itself and the HISTORY_doc/txt files) for you to try. Suggest you rename the originals in case you need to revert to them if this doesn't work. You may wish to config launchpad_obj to your preferred defaults with the CONFIG program.
If you confirm it works for you, Andrew, I'll add it to my Launchpad pages as an update.
Clearly there is a problem with the latest Qlib_ext and QJ; an earlier version works ok. Strange, 'cause I didnt (knowingly) alter any code, just repackaged it.
I'll try to fix it as soon as I have some time.
Clearly there is a problem with the latest Qlib_ext and QJ; an earlier version works ok. Strange, 'cause I didnt (knowingly) alter any code, just repackaged it.
I'll try to fix it as soon as I have some time.
100 DEFine PROCedure ListJobs(ch)
110 LOCal nj, n
120 :
130 n = 0
140 REPeat nj
150 n = NXJOB(n, 0)
160 IF n = 0: EXIT nj
170 PRINT#ch; JOB$(n)
180 END REPeat nj
190 END DEFine ListJobs
200 :
210 :
Thank you Per. I don't know why I didn't do something like that in the first place. Probably because I wanted to display the extra info that QJ or JOBS supply (and probably I was too lazy).
Clearly there is a problem with the latest Qlib_ext and QJ; an earlier version works ok. Strange, 'cause I didnt (knowingly) alter any code, just repackaged it.
I'll try to fix it as soon as I have some time.
This should fix it! There was one misaligned byte in the embedded text. I also removed some text that didnt belong there, but did no harm, so the toolkit is somewhat smaller (in case you were wondering).
So a query to y'all: Do I bump up the whole distribution a version number, ie to V3.37? It could be confusing with various components at different version numbers.. Perhaps include a version number within each component?
dilwyn wrote: ↑Mon Mar 18, 2024 10:02 am
<>
Thank you Per. I don't know why I didn't do something like that in the first place. Probably because I wanted to display the extra info that QJ or JOBS supply (and probably I was too lazy).
Ah yes. That was just a wee reminder in case you had forgotten. I knew you could fill in any missing details.
Clearly there is a problem with the latest Qlib_ext and QJ; an earlier version works ok. Strange, 'cause I didnt (knowingly) alter any code, just repackaged it.
I'll try to fix it as soon as I have some time.
This should fix it! There was one misaligned byte in the embedded text. I also removed some text that didnt belong there, but did no harm, so the toolkit is somewhat smaller (in case you were wondering).
So a query to y'all: Do I bump up the whole distribution a version number, ie to V3.37? It could be confusing with various components at different version numbers.. Perhaps include a version number within each component?
Personally, with the main QLib release at 3.45a (well, that's what it displays in its front end anyway) and the last Liberation Software distro at 3.36, I'd find 3.37 confusing.
dilwyn wrote: ↑Mon Mar 18, 2024 4:29 pm
Personally, with the main QLib release at 3.45a (well, that's what it displays in its front end anyway) and the last Liberation Software distro at 3.36, I'd find 3.37 confusing.
