You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You asked for testing on 4.30, so I tried it out on my system (macOS Sierra, GAP 4.10.0). The library works fine with Gap.app, at least in the limited testing that I tried.
With xgap running in Xquartz, I'm getting a beep everytime I click on a subgroup lattice window. That is, I open xgap, type "GraphicSubgroupLattice(AlternatingGroup(5));" at a prompt, and then choose a menu item or click in the poset diagram.
It looks like the beep is happening when output goes to the xgap command window. Typing e.g. "MenuSelected( 1, 2, 1 );" at the prompt doesn't give the beep.
I get the same in xgap 4.28, and the same behavior whether I start from Terminal.app or an xterm.
If you can't reproduce it easily, then I don't think it's worth worrying about; I report in case it is a broader problem.
The text was updated successfully, but these errors were encountered:
It seems to actually beep with many more interactions, e.g. when using the help system to browse through a list of relevant help items, and in other places.
Unfortunately I know far too little about the inner workings of xgap to effectively debug this :-(
You asked for testing on 4.30, so I tried it out on my system (macOS Sierra, GAP 4.10.0). The library works fine with Gap.app, at least in the limited testing that I tried.
With xgap running in Xquartz, I'm getting a beep everytime I click on a subgroup lattice window. That is, I open xgap, type "GraphicSubgroupLattice(AlternatingGroup(5));" at a prompt, and then choose a menu item or click in the poset diagram.
It looks like the beep is happening when output goes to the xgap command window. Typing e.g. "MenuSelected( 1, 2, 1 );" at the prompt doesn't give the beep.
I get the same in xgap 4.28, and the same behavior whether I start from Terminal.app or an xterm.
If you can't reproduce it easily, then I don't think it's worth worrying about; I report in case it is a broader problem.
The text was updated successfully, but these errors were encountered: