If you click on a word in the sentence (at the top of the screen), the
display scrolls to put the block for that word in the center of the
screen. That might save some scrolling-by-hand.
I see that there is a bug in that: it seems to put the block in the
center of the form, which puts it too low on the screen if the form is
taller than the screen. I'll fix it.
The 70-odd named locales in dissect are those that have code attached.
In addition, each noun/verb, including those created by compounds, gets
a numbered locale which is an instance of one of the named locales. The
paths of these locales are intertwined to select options for each. J's
locale/path system is well designed for this use.
Henry Rich
On 10/29/2019 2:37 AM, Gilles Kirouac wrote:
Having the rank of the verb in the status line is very helpful and
convenient.
As regards the vertical height, no real problem. A teacher can give
guidance on what follows. (I did not follow the labs myself).
While trying more complex expressions, I discovered that the graph can
be moved around. So to see the bottom of the graph if needed, just grab
it on white background and move it up. Wonderful!
The sentence ~. ; (#:i.2^4) <@(10 #. i.@!@# A. ])@# 0 1 2 6 (by Louis de
F) is very interesting to dissect, because with some duplicated glyphs
the pink boxes will tell which one is executed and also what the
interpreter handles first (which may not be obvious if you don't look
carefully enough).
Try dissect :
require 'debug/dissect'
dissect'~. ; (#:i.2^4) <@(10 #. i.@!@# A. ])@# 0 1 2 6'
Then introduce an error by suppressing the 6.
dissect is big. It uses more than 70 locales!
Le 2019-10-28 à 16:23, Henry Rich a écrit :
Fixing the window size when the tooltip detail is changed is enough of
a pain that I'm going to do leave it undone.
I have fixed it so that when you hover over a verb in the header, the
rank of the verb is displayed in the status line (which in Windows is
just to the right of the << < > buttons). Perhaps that will reduce the
need for verbose tooltips.
Henry Rich
On 10/28/2019 3:11 PM, Gilles Kirouac wrote:
After updating to dissect to 4.6.30, still using dissect '2 4 6 <@(]\)
''abcdefg'''.
If I switch from verbose to tutorial and there is not enough space
vertically for the full tutorial text, then there is no clue that the
text is incompletely displayed.
The rank of ]\ is of interest to the student. When my mouse is over that
verb in the graph, I want to know the rank of the verb which is 0 _. To
get it, I found no other way than using verbose or tutorial modes.
Le 2019-10-28 à 11:58, Henry Rich a écrit :
I put in some fixes for the problems you found.
Henry Rich
On 10/27/2019 7:48 PM, Gilles Kirouac wrote:
Yes, the window can now be resized and moved.
However if I widen the window, the pink boxes are now misplaced.
BTW, I think most users will adopt the verbose level since it displays
the ranks.
Le 2019-10-27 à 18:00, Henry Rich a écrit :
I see. I think dissect is leaving a lot of space for tooltips. Try
this:
dissect
Tooltips>Detail>laconic
Config>Save
close the dissect window
rerun dissect
Does that get you what you want?
I should make the window not go above the screen height unless
necessary. I will think about that.
hhr
On 10/27/2019 5:18 PM, Gilles Kirouac wrote:
See beta forum email.
~ Gilles
----------------------------------------------------------------------
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
--
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
