Search found 240 matches
- Tue Apr 21, 2020 10:04 pm
- Forum: Software & Programming
- Topic: QLiberator v3.38
- Replies: 22
- Views: 6617
Re: QLiberator v3.38
Here is my names re-order program ... names_order.zip REMark Program to Re-order names to match the original order : dev$ = "ram5_" : REMark change to suit : REMark dev$ & "QLIB_origina_obj" 46158 bytes REMark add in CLEAR somewhere to below BAS file, before LIBERATE / QSAVE ...
- Sun Apr 19, 2020 10:06 pm
- Forum: Software & Programming
- Topic: QLiberator v3.38
- Replies: 22
- Views: 6617
Re: QLiberator v3.38
Thanks for your work on this, Martin. It's looking good, now. This seems to cure the problems Per was talking about. I'm still trying to get my decompiled QLib to recompile as a copy of the original. To try to find what the differences are. But I'm having trouble getting the name lists to be created...
- Fri Apr 17, 2020 9:41 pm
- Forum: Software & Programming
- Topic: QLiberator v3.38
- Replies: 22
- Views: 6617
Re: QLiberator v3.38
EmmBee, Martin, There is still a problem with EXT_xxx, but the symptoms have shifted a bit. I find I get different results on QDOS-Minerva and QPC2. While it works on QDOS, on QPC2 I get error messages of "Keyword must be at start of program", even when EXT_PROC / EXT_FN is already at the...
- Fri Apr 17, 2020 7:13 am
- Forum: Software & Programming
- Topic: QLiberator v3.39
- Replies: 1
- Views: 936
QLiberator v3.39
Hi, We have a new updated version, which includes Dilwyn's scrxlim_cde. It occurs to me that the Patch program shares so many routines with Qlib_obj that every time Qlib_obj is updated there is a need to update the Patch program, as well. So, they have both been given the same version number, v3.39 ...
- Thu Apr 16, 2020 11:26 pm
- Forum: Software & Programming
- Topic: QLiberator v3.38
- Replies: 22
- Views: 6617
Re: QLiberator v3.38
You would be very welcome to use my SCRXLIM/SCRYLIM extension in QLib if it does what's needed of it. I'm afraid I don't know how QDOS on uQLx handles the bigger-than-512x256 screens, hence my note of caution. I suspect that the worst that would happen if there was no PE on uQLX running QDOS is tha...
- Wed Apr 15, 2020 7:52 pm
- Forum: Software & Programming
- Topic: QLiberator v3.38
- Replies: 22
- Views: 6617
Re: QLiberator v3.38
BTW: Line 32558: SCRXLIM = x : SCRYLIM = y Both VAR names will clash with Dilwyn's "scxlim.zip", where he used SCRXLIM and SCRYLIM as functions. I was perhaps going to use Dilwyn's code, but he has pointed out in his notes that it might not work for the uQLx emulator, which is an exceptio...
- Wed Apr 15, 2020 2:38 pm
- Forum: Software & Programming
- Topic: QLiberator v3.38
- Replies: 22
- Views: 6617
Re: QLiberator v3.38
Yes, use ... SETENV "QLIB_wA=" & wA : SETENV "QLIB_wD=" & wD where wA is the front end left x and wD is the top y position. I.e. top left corner.Derek_Stewart wrote:Hi,
Is there an environmental variable that can be preset to define the screen location of the compiler front end?
- Wed Apr 15, 2020 11:52 am
- Forum: Software & Programming
- Topic: QLiberator v3.38
- Replies: 22
- Views: 6617
QLiberator v3.38
Hi all, Attached is QLIB v3.38. I've added to the Release notes in the README file. Here is what I say ... RELEASE 3.37 March 2020 ------------------------- The past 27 years have witnessed huge strides in technology. Television and Monitor screen sizes have increased far beyond the original QL's 51...
- Sun Apr 12, 2020 8:57 pm
- Forum: Software & Programming
- Topic: New QLiberator v3.37
- Replies: 51
- Views: 16529
Re: New QLiberator v3.37
I've been reading the Q_Liberator Release Notes for RELEASE 3.31 June 1990. It contains this ... COMPILER CONFIGURATION Users who have a copy of the QJump level 1 configurator, config, can now use this utility to modify the compiler, QLIB_OBJ. The colour sheme and various compiler defaults including...
- Fri Apr 10, 2020 9:26 am
- Forum: Software & Programming
- Topic: New QLiberator v3.37
- Replies: 51
- Views: 16529
Re: New QLiberator v3.37
I've just discovered the error is caused by my skip_Top_Line_Remark routine at line 32492 in v3.37 Besides storing the file position, recording and then restoring the variables sym1%, sym2%, sym3, etc. seems to cure the problem. I'm currently in the process of checking all the code out for the v3.38...