Moving the mouse over the drawing area the same coordinates worked and placed the text where expected. New to me and different from your issue was, that entering coordinates for single line text didn't place the text while the mouse was outside the drawing area. And I don't remember if I ever used single line text, so this issue seems not depend on a single tool. This happens randomly for me, but I'm not a power user and I use the mouse or CTRL-m when it happens. Only CTRL-m brings back focus to command line then. What is known, is that at some point the command line isn't focused by keyboard input anymore. I recognized some strange behavior, some known, some new, but not exactly what you described. Playing around a bit, with your described steps, didn't trigger your issue for me yet. I assume that single line text is rarely used, because the tool bar icon, which presumably most users use, triggers MText, which may be better tested and not causing the issue. This bug report was produced against LibreCAD-2.2.0-rc3-55-g12dc3ea1-x86_64.AppImage My Linux distro is Mageia 8 (x86_64) and I'm using Plasma 5 (KDE Frameworks 5.76.0 Operating System and LibreCAD version info Closing the block and then reopening it for editing again provides you with a restored, functioning command line the same way closing and reopening the parent drawing would. If the bug triggers while adding text to that block, the command line of the underlying parent drawing remains unaffected, suggesting the bug is always confined to the window instance (sub-process or whatever you guys call it) the bug was triggered within. It may be meaningful to add that this bug will also trigger when editing a block from within a parent drawing. After the drawing is reopened, the command line will work okay again. LC itself does not need to be restarted in between. Once the bug has kicked in, the only way I've ever found around it is to save my drawing, close it, and reopen it. To test if this really is the case, just go through the same motions, all at the command line, as I've described above: a bit of pa here and a mv there - or heck, try to place a circle by keying in its center. I can practically guarantee (100% or your money back) that your command line is now borked in just the way I described above. Just (twice of course) out of the nested invocations so the prompt no longer reads "Specify insertion point".Īnd that's my newly patented Insta-Matic Bug Trigger™. Surprise! You're then presented with a second dialog from the other invocation. Hit OK to dismiss it (no other action is required). So here we go: Start a new drawing and run txt txt in your command line ( seriously, after all the hair I've pulled out over this, that's all there is to it). I don't know if there's a better or proper term for "nesting" in this context, so I'm metaphorically comparing the action to coding loops within loops within loops… Trying to reproduce this bug using only the mouse won't (as far as I can tell) trigger it. I haven't been truly clear about that prior to this edit. This bug is triggered by "nesting" one invocation of the text command inside another previously active one at the command line. Steps to reproduce (much revised and greatly clarified) You now notice that whatever tool you try to use or action you try to take, the command line will refuse and/or ignore all numeric input. You can keep entering 0,0 (or any other coordinates) all you want, but LC will never stop asking you to "Specify reference point". It's completely straight forward… Instead, this happens: So all you need to do is input 0,0 followed by 10,0 to bring up the Move/Copy dialog. In my own workflow, I'm a big fan of hammering absolute coordinates into the command line, especially for a simple adjustment like this. You want to shift this entity, say, 10 units to the right. You mouse click on an entity to select it. Say you need to place a new parallel line 50 units away from another, so you pa for parallel followed by 50 to satisfy the command's request to "Specify Distance", but: It still takes alpha characters as commands just fine, but appears to outright ignore their parameters. …now the command line has completely stopped accepting numeric input. Once you've labelled everything to your satisfaction or requirements you would expect to continue on with the next step(s) of your project, except… Observed behavior Maybe you've even changed your font choice along the way. You plop down a few labels here and there at various rotation angles and text sizes. So, say you're using the single-line text tool. I'm amazed I couldn't find an existing report for it. x series, and sadly, I can still reproduce it with the latest AppImage. I've been putting up with it since possibly even before the 2.1. Here's the next most annoying issue I have with LC off my List of Annoying Annoyances.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |