9

New bug in V 13.3

Wolfram support: A support case was created with the ID [CASE:5057959]

Why in V 13.3 on windows 10, when moving the mouse on top of a plot, it says there is an error? In V 13.2.1 the same code does not behave the same.

First, here is a small movies, then the code at the end.

V 13.3

enter image description here

V 13.2.1

enter image description here

Code

d={99.5305,98.6348,98.0392,98.1481,93.75,97.7778,78.9474,83.3333,91.6667,100.}
maxNumberOfSteps=10;
g=ListLinePlot[d,Frame->True,GridLines->{Range[maxNumberOfSteps],Automatic},GridLinesStyle->LightGray,Frame->{True,True,False,False},
   FrameLabel->{{"solved percentage",None},{"Rubi number of steps","Maple"}},
   Mesh->All,
   MeshStyle->Directive[PointSize[Medium],Red],
   PlotStyle->LightRed,
   PlotRange->{{1,maxNumberOfSteps},{40,110}},
   FrameTicks->{{Automatic,None},{Range[maxNumberOfSteps],None}},
   BaseStyle->Automatic,
   ImageSize->300]
Nasser
  • 143,286
  • 11
  • 154
  • 359

3 Answers3

5

Add

PlotHighlighting -> None

to prevent the feature of auto highlighting.

Or as my comment,using

ListPlot[..., Joined -> True]

Edit

This bug have been fixed in v13.3.1 enter image description here

cvgmt
  • 72,231
  • 4
  • 75
  • 133
3

As an alternative, you can use Plotmarkers instead of Mesh.

With[{d = {99.5305, 98.6348, 98.0392, 98.1481, 93.75, 97.7778, 
    78.9474, 83.3333, 91.6667, 100.}, maxNumberOfSteps = 10},
    ListLinePlot[d, Frame -> True, GridLines -> {Range[maxNumberOfSteps], Automatic}, 
    GridLinesStyle -> LightGray, Frame -> {True, True, False, False}, 
    FrameLabel -> {{"solved percentage", None}, {"Rubi number of steps","Maple"}},
    PlotMarkers -> Automatic, PlotStyle -> LightRed, 
    PlotRange -> {{1, maxNumberOfSteps}, {40, 110}}, 
    FrameTicks -> {{Automatic, None}, {Range[maxNumberOfSteps], None}}, 
    BaseStyle -> Automatic, ImageSize -> 300]
]

enter image description here

david
  • 1,290
  • 1
  • 10
  • 15
1

The "bug" is removed by

Mesh -> {All, All}

Generally the "All" directive was working on list output, too, where the normal input would require a directive for each entry. There seems to be a conflict between Graphics and mouse coordinate supply by interaction now.

AsukaMinato
  • 9,758
  • 1
  • 14
  • 40
Roland F
  • 3,534
  • 1
  • 2
  • 10
  • 4
    With version 13.3.0 for Mac OS X ARM (64-bit) (June 3, 2023) and using Mesh -> {All, All}, I get the message Mesh::ilevels: All is not a valid mesh specification. and there are no mesh points. – Bob Hanlon Jul 03 '23 at 16:03
  • 2
    I also get an error Mesh::ilevels: All is not a valid mesh specification. on V 13.3, so this is does not remove the bug? I am on window 10. – Nasser Jul 03 '23 at 18:50
  • 1
    Does not work on Windows 11. And the result just as set Mesh->None – cvgmt Jul 04 '23 at 02:02
  • https://community.wolfram.com/groups/-/m/t/2950027 – Dennis La Cotera Jul 04 '23 at 02:30
  • 3
    This answer should be removed since it (1) doesn't answer the user's question and (2) contains errors – Jason B. Aug 18 '23 at 13:20
  • The bug still exists in 13.3 (today), the original code is diplaying a Graphics ouptut in pink background (error) and the Mesh->{All,All} still is working. Neither your (1) nor (2) are true. So´why do you think to remove the answer? – Roland F Aug 18 '23 at 14:45