The Sinclair QL Forum

After 27 years we now have an update to Q_Liberator. The last version was v3.36. Brilliant work, well done everyone involved. Might I suggest that the source code etc be uploaded to the SinclairQL github repository for future use? https://github.com/SinclairQL I'm happy to do this for you if you ne...

Hi everybody, After 27 years we now have an update to Q_Liberator. The last version was v3.36. There are 4 main additions with this latest v3.37 update … + Now able to move QLIB’s front panel around outside of the previous 512x256 limit. + Longer filename entries - up to the maximum of 41 chars allo...

But if you have ended the compilation, press space, move the window, stop the program, EX it again, the position is as you have left. So the data must be written after every move and return to QLIB_BIN (as QLibs ALCHP is lost of course when you stop the program). QLibs ALCHP does not get lost - as ...

If, every time a new QLIB compile is started, the above line is executed, then that location would be overwritten with zeroes. Does it perhaps need to be used once only in a BOOT file? That way, all the info would remain intact. But if you have ended the compilation, press space, move the window, s...

I've also found out how to move the console around outside of the 512x256 rectangle, except for the QLIB_USE giving an error message when the window is closed. I think, this error comes, because QLib's Pointer I/F extensions use a little data block in memory to save the main windows position on scr...

This is a continuation from the thread .. https://qlforum.co.uk/viewtopic.php?f=3&t=3123 I could start by taking a look at NEXT_TOKEN. Im no assembler ace, mind you! so if anyone more capable wants to volunteer say so now, otherwise I'd like to put a lock on it until further notice. EmmBee, perh...

pjw wrote:Whops! This should probably have gone in the other thread!

Perhaps we should create a new thread - New QLiberator v3.37?

<> I've now completed my efforts, renaming Martin's Q_Liberator decompile. This was posted on the decompiler thread. So, I thought I would also post it here in case you missed it and for everyone else who would like to see this. I believe I have got the vast majority of the meanings correct. There ...

Ralf R. wrote:

EmmBee wrote:

Ralf R. wrote: Which ones? There are so many....

I usually visit Dilwyn's website for most of my QLIBs.

I meant the patch programs from WLs site. There are a few with similar names.

Can you give us a link?

NEXT_TOKEN is a more complex code as it contains a table of offsets (14 entries) and jmp is made to one of these locations. So we have to pull out all these jumped codes also. This new archive contains the complete assembler for NEXT_TOKEN. Alain DeaQlib2.zip Hi Alain Thanks for this code. We are n...