Page 1 of 1

SharpPlot extremely sluggish in APL v18.2

Posted: Sun Jun 26, 2022 5:11 pm
by KamakaniKing
When using SharpPlot via the Chart Wizard in APL v18.2, SharpPlot responsiveness is extremely slow: up to 15 - 20 seconds for plot updates and chart setting changes. Same data plotted in APL v18.0 is very fast.
Also upon exiting the Chart Wizard in v18.2 and attempting to save the workspace, I get the following error:
Cannot perform operation when # is referenced by session namespace.
Reached via:
⎕SE.tip...THIS


I'm using the following code to generate 6 sine waves on a single graph (y1 vs. x):
      x←0,(⍳200)×○÷100
n←⍳6
y←0.3×1○(0.5×n)×⍤0 1⊣x
y1←n+⍤0 1⊣y

Is anyone else having these issues with v18.2?

Re: SharpPlot extremely sluggish in APL v18.2

Posted: Mon Jun 27, 2022 10:53 am
by Vince|Dyalog
Hi KamakaniKing,

Thanks for reporting these issues.

The save issue due to "Cannot perform operation when # is referenced by session namespace" is logged as 12649.

I have logged the SharpPlot wizard slowness as 19908.

Regards,

Vince

Re: SharpPlot extremely sluggish in APL v18.2

Posted: Fri Apr 07, 2023 4:24 pm
by ray
The save issue due to "Cannot perform operation when # is referenced by session namespace" is logged as 12649.
I seem to get this error every time I "Exit" from Chart Wizard.

What do I need to do to get past this error?

Simply starting Chart Wizard in a clear workspace, then selecting Exit from the menu to end it without any other interactions (other than replying to "are you sure") causes it on a )clear

Code: Select all

Clear
<< click on the chart wizard icon >>
        )clear
Cannot perform operation when # is referenced by session namespace.
Reached via:
⎕SE...THIS
Thanks for any suggestions.
Ray

Re: SharpPlot extremely sluggish in APL v18.2

Posted: Tue Apr 11, 2023 8:16 am
by Vince|Dyalog
Hi Ray,

There are two workarounds that you can try.

1)
)reset

2) A more complicated option is to temporarily destroy the contents of ⎕SE.

)cs ⎕SE
⎕ex ⎕nl 9
⎕WA
)cs

Please remember not to save the Session configuration or session file at this point.

At this point, you can try to )save the workspace.

If you cannot )save, you can try this command to an already existing directory of your choice. In my example, I use c:\tmp\
+2 ⎕nq '.' 'dumpws' 'c:\tmp\mycor.cor'

This method creates an aplcore-like file that you should be able to ⎕cy objects out of.

Regards,

Vince