The Sinclair QL Forum

Version 3.46 of the Q-Liberator compiler is now available to download from https://dilwyn.qlforum.co.uk/qlib/index.html

The source files are also available on the page.

<> 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 ...

Dilwyn, you could try: 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 p...

pjw wrote: ↑Sun Mar 17, 2024 10:41 pm

pjw wrote: ↑Sun Mar 17, 2024 10:07 pm <>

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.

Thank you Per.

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 Qliberato...

Have been looking at this today without yet being able to resolve the issue. The Jobs menu is populated by sending the output of the QLiberator QJ command to a pipe channel and reading back the results, using Q_PIPE . Somewhere amid this, things just stop for no obvious reason. Interestingly, it do...

Have been looking at this today without yet being able to resolve the issue. The Jobs menu is populated by sending the output of the QLiberator QJ command to a pipe channel and reading back the results, using Q_PIPE . Somewhere amid this, things just stop for no obvious reason. Interestingly, it doe...

I don't want to overcomplicate things, but I wrote an article on how the font data structures work (in broad terms) which might help to explain why PEEKing and POKEing font addresses is a bad idea. It's a bit technical but tries to explain things as it goes along. If it helps explains things, I migh...

Derek_Stewart wrote: ↑Sat Mar 16, 2024 2:06 pm Hi,

Have look at QL Today Vol13 issue 2,3,4 Dilwyn did an excellent article on the use of Fonts.

Article available here.
https://www.dilwyn.qlforum.co.uk/docs/a ... nfonts.zip

Thank you, Andrew. Iwill try to resolve this over the next few days.