Slow update of the "CurObj"

APL-related discussions - a stream of APL consciousness.
Not sure where to start a discussion ? Here's the place to be
Forum rules
This forum is for discussing APL-related issues. If you think that the subject is off-topic, then the Chat forum is probably a better place for your thoughts !

Slow update of the "CurObj"

Postby ray on Fri Jun 14, 2024 12:18 pm

Hi,

I use Dyalog under Windows (currently Dyalog APL/W-64 Version 19.0.48959).

In many of my tools, I use "CurObj" (a property of ⎕SE) and have been doing since the Dyalog version it was introduce. (Dyalog version 7 ?)

If I "click" on the name on a function in the session (say "MouseUp") , CurObj used to appear to be updated instantly to say
CurObj: MouseIp (Function)
.

One of my tools is RootFind. RootFind can be access via functions in ⎕SE.Ucmd (Similar to, but predating Dyalog's ⎕SE.UCMD).

⎕SE.Ucmd copies a workspace called RootFind.DWS into a temporary namespace under ⎕SE. The code in this namespace then "reads" ⎕SE.CurObj. It then proceeds to search the Root (#) and all it's sub-namespaces, for the name supplied by CurObj. RootFind then display the function names that mentions the CurObj.

I use this feature (and similar tools) multiple times in a session. I use these tools for several reasons: It is faster than simply typing the name; I am dyslexic; I cant remember how I spelt the name; I prefer to use the mouse than the keyboard (Im a poor typist, and getting worse as I get older); and I am lazy!

Recently I have found that CurObj is taking a significant time (more than a second) to be updated. (Last time I tried it, I was able to count to count to 4 before it was updated!)

It is now so slow that after selecting a object to find (which should update CurObj), and then pressing a menu set to to run RootFind , RootFind proceeds to search the un-updated value in CurObj.

I have tried reducing my WS size from 2G to 4M but it still appears just as slow.

I don't have "Value Tips" set.

I have tried turning off AutoComplete.

I can imagine that CurObj's priority has been reduced to speed up some other priority.

Is there anything I can do to speed CurObj up, via some setting maybe?

Thanks for any feedback

Ray
Ray Cannon
Please excuse any smelling pisstakes.
User avatar
ray
 
Posts: 234
Joined: Wed Feb 24, 2010 12:24 am
Location: Blackwater, Camberley. UK

Re: Slow update of the "CurObj"

Postby ray on Fri Jun 14, 2024 12:20 pm

Opps,
CurObj: MouseUp (Function)
Ray Cannon
Please excuse any smelling pisstakes.
User avatar
ray
 
Posts: 234
Joined: Wed Feb 24, 2010 12:24 am
Location: Blackwater, Camberley. UK


Return to APL Chat

Who is online

Users browsing this forum: No registered users and 1 guest