The Sinclair QL Forum

I would also like to add my thanks to all those who have given us, often silent users of QLiberator, access to the source and updated for modern SMSQ/E systems.

One of my beefs with using QLiberator on my QPC2 SMSQ/E system is the rather old QRAM style colour of the QLiberator panel. So I decided I ...

Thanks for the response Per.

Yes, that avoids the problem, but I still find it strange that MINOB should impact application window attributes.

Never mind, rather than spending time on something I can avoid, I'll get back to my project...

Hi,
While tinkering with a little program, I've noticed strange behaviour with the colour attributes of application windows following the setting of text in an information object. I'm not exactly sure what is going on, but I'm pretty certain that setting an information object using MINOB should not ...

Try this, call with channel and application window number and xsize% and ysize% are returned. Hope that give you what you want.

DEFine PROCedure GET_APPW_SIZE(channel,appw_no,xsize%,ysize%)
LOCal working_def,ww_nappl,ww_pappl,apw
:
working_def=MWDEF(#channel)
:
ww_nappl=PEEK_W(working_def+HEX ...

mk79 wrote:I will bet my ass on the fact that Tony wouldn't mind this being available for free, I just don't have a distribution at hand.

A bit late with my response, but it would be very good if QTYP could be made available.

This is really good work.

I've loaded it and given it a quick try and noticed (no criticism implied!):
a) Loading takes several seconds (about 5), the previous version was pretty much instant. Is that expected?
b) You can move beyond original screen, but the saved position is still within the ...

Not sure where I got this from but here is my PDF copy

It is in one (or both) of QLE or Black Phoenix. I'm not sure whether it is public domain, but it is there. Unfortunately, I can't check which it is in at the moment.

After the sources were released I has a very quick look at the "moving beyond original screen" issue.

The code appears to have some checks in it, but these on their own are not enough to fix it (as has already been mentioned). I suspect the limit may be checked in QLIB's pointer routines also ...

Well, true to form this was my mistake.

$$asmb=name,0,60 does work. As the QLiberator manual clearly states, the extension (in this case APPA0) must be loaded when compiled. However, I had QSAVE'd before loading it and compiling it. I always save code using QSAVE so never use the LIBERATE name ...