Thanks Bill,

This is the verb that I modified from Henry's invocation of dissect.

 findline =: 3 : 0    NB. WinSelect is a character index; WinText is entire 
window; if window contains non-ASCII, convert to unicode
  if. y do. ; }. ;:(#~ -.@:(*./\)@:=&' ') ": > {: < ;. _2 (wd'sm get 
inputlog'), LF NB. pull the last line only for the monadic case Programmatic 
version strip off first word which would be invoking verb
        else. (#~ -.@:(*./\)@:=&' ') ": ({. WinSelect_jqtide_) 
((LF&taketo&.|.)@:{. , LF&taketo @:}.)  7 u: WinText_jqtide_  end.NB. The line 
that the cursor is on if 0 - Function key version
)

I believe that WinSelect_jqtide_ is the other name that is used that may be 
affected.

Cheers, bob

> On Dec 13, 2020, at 23:50, bill lam <[email protected]> wrote:
> 
> understood. There are some undocumented names or that I failed to notice
> inside the source of qtide frontend. Those names are not refernced insude
> the frontend itself so I didn't handle them.  Are there any other special
> names that you are using?
> 
> On Mon, Dec 14, 2020, 3:36 PM 'robert therriault' via Programming <
> [email protected]> wrote:
> 
>> Thanks Bill,
>> 
>> In jig, coname '' returns the locale that you are in when when you invoked
>> jig.
>> 
>> I have tested it in both the jig 901 and jig 902 versions and the result
>> of coname '' confirms this.
>> 
>> I have also noticed that WinText_qtide_ is no longer defined
>> 
>>    WinText_jqtide_
>> |value error: WinText_jqtide_
>> 
>> Since I use that to select the information from the line that the cursor
>> is on, it is quite possible that this is the source of the problem. Is
>> there a reason that WinText_jqtide_ would not be defined?
>> 
>>    JVERSION
>> Engine: j902/j64avx2/darwin
>> Release-a: commercial/2020-12-05T12:43:38
>> Library: 9.02.08
>> Qt IDE: 1.9.1/5.12.10(5.12.10)
>> Platform: Darwin 64
>> Installer: J902 install
>> InstallPath: /users/bobtherriault/j902
>> Contact: www.jsoftware.com
>> 
>> Cheers, bob
>> 
>>> On Dec 13, 2020, at 22:12, bill lam <[email protected]> wrote:
>>> 
>>> I'm unfamiliar with dissect and PFkey.
>>> PFkey behaves differently under suspension mode or not.
>>> 
>>> Your syntax seems correct. IIRC when running under non suspension mode,
>>> commands are executed as a script with empty stack. Can you check what is
>>> the value of coname'' when calling PFKey?
>>> 
>>> 
>>> On Mon, Dec 14, 2020, 1:38 PM 'robert therriault' via Programming <
>>> [email protected]> wrote:
>>> 
>>>> J902 is up and running on my system. Thank you to the team for all of
>> the
>>>> work that goes into this process. I hope that you all have a relaxed
>>>> holiday season after so much work.
>>>> 
>>>> One question. Now that the issue with PF keys has been fixed, what is
>> the
>>>> process for assigning applications like dissect to PF keys. The previous
>>>> approach described in the wiki results in
>>>> 
>>>> 
>>>> |noun result was required: finddissectline_dissect_
>>>> |       1<#~.fs
>>>> |[-0]
>>>> 
>>>> The wiki suggests using
>>>> F2;0;Dissect Line;dissect&.finddissectline_dissect_ 0
>>>> 
>>>> I use this for my jig augmented display
>>>> F6|0|Jig Augmented Display|((1 ; coname '') visual_jig_ 0)
>>>> and it returns a similar result.
>>>> 
>>>> Any suggestions that you have would be welcome.
>>>> 
>>>> Cheers, bob
>>>> 
>>>>> On Dec 13, 2020, at 15:36, Henry Rich <[email protected]> wrote:
>>>>> 
>>>>> The new version of JQt does not require the ugly workaround for PFkeys
>>>> in debug that the previous version required.
>>>>> 
>>>>> Henry Rich
>>>>> 
>>>>> --
>>>>> This email has been checked for viruses by AVG.
>>>>> https://www.avg.com
>>>>> 
>>>>> ----------------------------------------------------------------------
>>>>> For information about J forums see http://www.jsoftware.com/forums.htm
>>>> 
>>>> ----------------------------------------------------------------------
>>>> For information about J forums see http://www.jsoftware.com/forums.htm
>>>> 
>>> ----------------------------------------------------------------------
>>> For information about J forums see http://www.jsoftware.com/forums.htm
>> 
>> ----------------------------------------------------------------------
>> For information about J forums see http://www.jsoftware.com/forums.htm
>> 
> ----------------------------------------------------------------------
> For information about J forums see http://www.jsoftware.com/forums.htm

----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm

Reply via email to