LDCad Possible bug when selecting/rotating?


Possible bug when selecting/rotating?
#1
EDIT: Definitely an issue on my end, and not a bug at all. I don't want to cast any undue criticism on this very fine program!  Wink

I'm having a little trouble with the interface, and I'm guessing it's because I'm running LDCad on MacOS under Wine, but maybe it's a known bug, or perhaps my own error. There are two symptoms that appear to be related:

  • Selecting: Normally, [left-]clicking a part will select it, or if it's already selected, will deselect it. Also, if a part is selected, clicking a different part will select that part while deselecting the first part. But quite often, these behaviors will stop working, and the only way I can proceed is to "force" deselect everything by pressing ESC—sometimes more than once, and even if nothing is currently selected. This doesn't happen every time, and seems to occur more often in certain models than in others.
  • Rotating: Normally, dragging the empty part of the edit window will rotate the camera. But again, sometimes this stops working and I have to hit ESC to proceed (when this happens, dragging the edit window will simply scroll/pan the view). Often, it will still be possible to rotate the camera by dragging the edit compass, but other times, neither the compass nor the window works; and again, sometimes it's necessary to hit ESC multiple times.
I'm trying to figure out if there's any predictable cause, but in the meantime, is there a known reason that things might get "stuck", and why releasing them by pressing ESC seems to work? (One thing that might be relevant is that, since I don't have an INSERT key, I've set up my own hotkey for that purpose. I use command+enter, which LDCad calls alt+enter. The problem does seem to occur when I use this hotkey a lot, but that might be a coincidence because any editing session involves a lot of inserting.)

Any ideas? Anyone else have a similar issue?

UPDATE: It happened just now, where one part was stuck selected. Clicking in the edit window didn't do anything, but clicking other parts in the source window had an effect as if I'd shift-clicked (adding the new part and all parts in between to the selection). So it's as if LDCad thinks the shift key is pressed when it isn't (which would also explain the panning instead of rotating).
Reply
RE: Possible bug when selecting/rotating?
#2
Quote:So it's as if LDCad thinks the shift key is pressed when it isn't (which would also explain the panning instead of rotating).
Could it be a sticky key issue caused by triggering some accessibility feature? I had that kind of problem from time to time (not related to LDCad).
Reply
RE: Possible bug when selecting/rotating?
#3
(2020-03-17, 17:24)Philippe Hurbain Wrote: Could is be a sticky key issue caused by triggering some accessibility feature? I had that kind of problem from time to time (not related to LDCad).

I'm leaning in very much that direction. I suspect now that it's related to the hotkey I'm using for the Mac's desktop switching feature, which also uses the Shift key. I'm going to try changing that hotkey back to using Option instead of Shift, since I don't believe Option can be used for hotkeys in LDCad. If that works, then it's just a matter of remembering why I changed from Option to Shift in the first place!  Tongue
Reply
RE: Possible bug when selecting/rotating?
#4
(2020-03-17, 19:11)N. W. Perry Wrote: I'm leaning in very much that direction.

I'm no mac expert but can't you just disable the feature?

Sticky shift is one of the first things to go in a clean windows setup for me too Smile
Reply
RE: Possible bug when selecting/rotating?
#5
(2020-03-17, 21:48)Roland Melkert Wrote: I'm no mac expert but can't you just disable the feature?

Sticky shift is one of the first things to go in a clean windows setup for me too Smile

I could indeed, but it's so integral to my workflow that it would be much more disruptive to disable the feature than to just live with the issue. (Cutting off the nose to spite the face, as it were.) But if we've correctly identified that as the culprit, it looks like I won't have to do either; changing the hotkey should do the trick!
Reply
« Next Oldest | Next Newest »



Forum Jump:


Users browsing this thread: 1 Guest(s)