
Might be a good idea to refresh the old RAM again, by going through the list! However, it doesnt look like the list has been updated since about SMSQ/E V2.99. (Probably my fault for not doing my bit..

Code: Select all
(SMSQ/E)
3.34
JOB_NAME - Updated: works for compiled tasks too. Can
change name at any time (like QPAC2 Files). Up to 48 char.
SUSJB - Suspend a job for a given number of ticks.
-1 => infinite. Same parameters as other
TK2 job commands. (Also in TK2 2.32)
FDEL - Function versions of DELETE (may not have
made it into 3.34 and TK2 2.32)
3.30
JVA_IS_QLSCREMU%
DISP_MODE - Q40
3.28
JVA_VER$ - Java
JVA_WINDOWTITLE
JVA_NETNAME$
3.24
JVA_SCRUPDT - (Java)
JVA_MBAR_STATUS - (Java)
3.22
FEX_M - Function version of EX_M (see below)
3.16
WM_MOVEALPHA - Move/Copy a block of screen data with
alpha blending
3.13
YEAR%, MONTH%, DAY%, WEEKDAY%
3.12
PEEK_F, POKE_F
PEEKS - PEEK supervisor
JOBID - Job ID. Same parameters as for other TK2
job commands
3.09
GET_HOTSTUFF$ - function to get strings from stuffer
buffer. 0 => current, -1 => previous
3.07
EX_M - EXECute file with me as owner. Like
EXEC_W, but without the _W
3.06
QUIT - Takes optional error code parameter. Eg
er = FEW(mylittle_job). If mylittle_job quits with QUIT -15, er = -15.
3.00
FEX, FEW, FET - Function versions of EX, EW, ET. FEX and
FET return ID of (first) job in a chain. FEW returns any error from job.
Unknown when introduced:
WM_PAPER - the following 5 keywords use the Window
WM_STRIP Manager palette colour codes
WM_INK
WM_BORDER
WM_BLOCK
WM_MOVEMODE - parameter 0..3. Different ways of moving a
window, from the old-fashined move an icon, to moving a semi-transparent window.
SP_GETCOUNT - Get number of palette entries (currently 57)
SP_JOBOWNPAL - Set a job's private palette (address)
SP_JOBPAL - Set a job to use a system palette, 0..3
SP_GET - SP_GET [number,] address, first, count
Gets the colours from a system palette and puts them somewhere.
SP_SET - SP_SET [#channel,] [number,] address, first, count
Sets the system palette entries
SP_RESET - SP_RESET [#channel] [,number]
This resets the colour palette given in number to the original values (as
configured). Default is number 0.
tofro wrote:I'm not sure if EasyPtr (and QPTR) should actually go into the S*BASIC reference manual - They have (pretty good) manuals of their own and I somehow feel a full introduction into PTR programming might be well beyond the scope of the S*BASIc manual.
NormanDunbar wrote:
- Make sure that the toolkit names in the individual keyword pages are standardised. We have, for example, 'Tiny Toolkit', 'TinyToolkit' and 'Qview TinyToolkit' - presumably all for the same toolkit? I've assumed this to be the case in the Toolkits page, and merges them all under TinyToolkit at https://superbasic-manual.readthedocs.i ... inytoolkit.
pjw wrote:tofro wrote:I'm not sure if EasyPtr (and QPTR) should actually go into the S*BASIC reference manual - They have (pretty good) manuals of their own and I somehow feel a full introduction into PTR programming might be well beyond the scope of the S*BASIc manual.
Im aware of your point , Tobias. I just think that the selection of keywords and toolkits in the manual is somewhat lopsided, and underrepresents lets say, a different outlook on what S*BASIC programming is or can be. Why is the Turbo toolkit in and QLib out? A number of post-V2.99 SMSQ/E keywords have made it into the manual, but others have not. Im not suggesting that these are deliberate choices, just that in total, they represent a "view". PI and Wman are now part of the "QL", ptrmen and Qptr are the only toolkits that make these systems accessible to many S*BASIC programmers. A number of rather arcane and obscure toolkits have made it into the manual, presumably in a bid to make it a comprehensive, if not THE definitive, manual. If that is the case, omitting these important system extensions would be odd, IMHO.
Users browsing this forum: No registered users and 0 guests