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
I don't have a reliable way to reproduce this. Every so often when I'm working on something and I try to cut some text (command-x), Boxer will hang (spinning beachball). To get Boxer back into a good state, I end up having to force quit Boxer and reopen it. I usually end up losing some work when this happens because my last save was a few minutes or so back. As a user of Boxer, this is probably the highest impact bug I've come across.
I haven't come up with a reliable way to reproduce it. It happens every so often as I work but I haven't noticed any patterns so far that would help create a reliable repro.
Do you have any tips on how we might go about capturing and tracking down this bug?
The text was updated successfully, but these errors were encountered:
Sorry, this does sound truly frustrating. Is it just Cut... do you ever notice this on Copy operations?
Is there any pattern you've noticed? Are you cutting large amounts of things, perhaps Boxes or shrunken boxes that have large contents?
I'm thinking about what kind of debugging/error output could be fetched from this scenerio (and perhaps some better logging/logfile that could be made available in the future).
I'm using Boxer
3.4.19 2024-06-24
on macOS.I don't have a reliable way to reproduce this. Every so often when I'm working on something and I try to cut some text (command-x), Boxer will hang (spinning beachball). To get Boxer back into a good state, I end up having to force quit Boxer and reopen it. I usually end up losing some work when this happens because my last save was a few minutes or so back. As a user of Boxer, this is probably the highest impact bug I've come across.
I haven't come up with a reliable way to reproduce it. It happens every so often as I work but I haven't noticed any patterns so far that would help create a reliable repro.
Do you have any tips on how we might go about capturing and tracking down this bug?
The text was updated successfully, but these errors were encountered: