'===========================================================================
' Author: bruceuncle
' Date: 10/06/2015
'
' MUST be used as an accessory
'
' Tokenise current line in the editor using the current cursor position as
' the starting point for the text.
' Results in a tokenised line of code as if just that text had been entered.
' The 1st word in the result can be discarded as it will be out of context
' with the actual line of code if the starting position is not at the
' beginning of a line.
'
' So this can replace the text-intensive scanning that the existing help
' system uses:
'
' Step 1 - Get the tokenised code.
' Step 2 - Exclude "punctuation" tokens (anything from $FF37 thru $008C).
' Step 3 - Get the first "real" token and check for Tk_Ext ($004E) to see
' if it's an extension library token.
' Step 4 - If it's not an extension, job done, use extension 0 and go
' to Step 6.
' Step 5 - If it is an extension, get the extension's number and its
' internal token number.
' Step 6 - Use the extension number to select the appropriate help files.
' Step 7 - Look up the help text using a new-format "*.map" file and the
' token number. This can now be a binary search against an
' ordered list of token numbers for each library instead of the
' current linear text search.
'
' The new-format "*.map" file is an array of fixed-size records:
'
' (0) Word - Token Number.
' (2) Word - Help Text Length.
' (4) Long - Help Text starting offset in "*.txt" file.
'
' The benefits are that extension libraries can participate in help
' simply by supplying appropriate "*.map" and "*.txt" files.
'
' Menu and info links can use any token below $FF37.
'
Set Accessory
' Offset to Buffer(a5)
Global GC_BUFFER
GC_BUFFER=$4F2
Screen Open 1,640,256,16,Hires
Wait Vbl
Screen 1
' Ask for the current line
Ask Editor 1
G_LINE$=Param$
' Ask for the current cursor position in the line
Ask Editor 3
G_CURS_X=Param
' Derive the text from current cursor position onwards
G_TEXT$=Mid$(G_LINE$,G_CURS_X)
' Get the address of Buffer(a5)
G_BUFFER_ADDR=Leek(Areg(5)+GC_BUFFER)
' Poke the text into the buffer
Poke$ G_BUFFER_ADDR,G_TEXT$
Poke G_BUFFER_ADDR+Len(G_TEXT$),0
' Ask for the address of the tokenised result
Ask Editor 12
G_ADDR=Param
' Display the results
Print
Print "Original line complete : ";G_LINE$
Print "Cursor position in line : ";G_CURS_X
Print "Text at cursor : ";G_TEXT$
'
' Offset Type Description
' ====== ==== ===========
' (0) Unsigned Byte Length of tokenised line in WORDS.
' (1) Unsigned Byte Starting position of line (encodes leading spaces).
' (2) Signed Word 1st Token, if it's $004E, it's an extension library
' token.
' (4) Word Next token, token data or, if 1st token was $004E
' next byte is Extension Slot Number.
' (6) Word Next token, token data or, if 1st token was $004E
' this word is that Extension's Token.
'
' And so on until end of text
'
Print "First 8 words of tokenised line:"
Print Mid$(Hex$(Peek(G_ADDR),2),2);" ";
Print Mid$(Hex$(Peek(G_ADDR+1),2),2);" ";
For I=2 To 15 Step 2
Print Mid$(Hex$(Deek(G_ADDR+I),4),2);" ";
Next I
Print
Wait Key
Screen Close 1
How do i go about producing an AMCAF help file? ;)
' The new-format "*.map" file is an array of fixed-size records:
'
' (0) Word - Token Number.
' (2) Word - Help Text Length.
' (4) Long - Help Text starting offset in "*.txt" file.
Sounds brill - I am pretty adept at VBA coding, so I could probably convert the HTML version of the AMCAF manual into this format fairly easily.
I will just need to look at a couple of example .txt entries to "program" the layout right.
I don't see any issues, unless a specific piece of help text exceeds 65,535 characters... but I think that is going to be highly unlikely :)Sorry to take a while to reply. Life's been getting in the way a bit - see here (http://www.ultimateamiga.co.uk/index.php/topic,9814.msg47048.html#msg47048).
I code access databases for about 65% of my working days...Hey! Another Access programmer. I thought we were as rare as AMOS programmers. ;) I've known lots of people who "use" Access but few who actually program it.
The reason for looking at it whilst in the midst of the editor is getting the editor to scroll from a mouse wheel, which requires two new editor command functions in the editor config. There's spare slots, so not too taxing. Otherwise, getting the file selector to scroll from a mouse wheel was an easy DBL fix.
hey, I just got the scroll wheel working in the editor by recording a macro - yehI must admit I never thought of that as a quick fix.
| 1 | System File Names | +Edit.s .Sys1 thru .Sys2: |
| 2 | Menu Messages | +Edit.s .Mn1 thru .Mn2 (from "Editor_Menus.Asc") |
| 3 | Dialog Messages | +Edit.s Ed1 thru Ed2 |
| 4 | Test-Time Messages | +Edit.s .Test1 thru Test2 |
| 5 | Run-Time Messages | +Edit.s .Error1 thru .Error2 |
| dc.l | MessageNumber |
| dc.b | Replacement string |
You say you have done this for the File Requester - I know this is in +W.s but I can't find any edits - would be great to get the file selector working as well...Almost all of the screen handling and all of the requester handling is done using DBL (Dialogue Box Language) code hidden away in Resource Banks. This code is a bugger to read and edit, so I wrote a DBL editor a long while ago to make it easier to edit and document. The thread is here (http://www.ultimateamiga.co.uk/index.php/topic,9642.msg45318.html#msg45318). It's slightly buggy but does the job. Read the thread for more info. The zip file includes a *.guide which is essential reading before using!!!