|
1920 | QCAD (main) | Feature Request | Very Low | Edit > Application Preferences: Add preference to disab... | Assigned | |
|
Task Description
See also: https://www.qcad.org/rsforum/viewtopic.php?f=89&t=6447
|
|
1922 | dwg2bmp | Feature Request | Very Low | Add error message when requesting raster for a non-exis... | Assigned | |
|
Task Description
It would be nice if QCAD spit some kind of warning message when trying to render a layer with a name that doesn’t exist (and perhaps render nothing), rather than silently rendering an empty image. :D
See https://qcad.org/rsforum/viewtopic.php?f=33&t=6453
|
|
1930 | QCAD (main) | Feature Request | Low | Option disable "Auto Zoom on load" for saved "Layout Vi... | Assigned | |
|
Task Description
Hi,
my setting for “Auto Zoom on load” is checked to on. That works perfect for me for most of my drawings.
But if I save a drawing with Layout Viewports then I have to adjust every Viewport again after loading.
Would it be possible to have an option below Application Preferences / Graphics View / Appearance / Auto Zoom on load / ON which excludes drawings saved with Layout Viewports?
|
|
1934 | QCAD (main) | Feature Request | Low | Diametric text - overlaid | Assigned | |
|
Task Description
Diametric text is always placed above a horizontal measurement.
I often want to indicate both the inside and outside diameter of an object e.g. a wheel using diametric text. The text is overlaid and illegible.
To avoid text overlapping, I use Horizontal Aligned because I can control the position of the text to avoid illegible text.
A better method would be to alternate the placement of diametric text (alternatively) above and below a measurement so that in the majority of cases an overlap would be avoided.
Similarly for a vertical measurement, the text is overlaid and illegible.
When the angle is almost vertical, the angle controls the side the text appears however it also reverses the direction of the text (which is logical but not attractive).
Kind regards Simon
|
|
1982 | QCAD (main) | Feature Request | Low | measure DIN 1356 | Assigned | |
|
Task Description
To measure in the format DIN 1356 , Architect It is hard work to do this manual input with meta characters.
|
|
2034 | QCAD (main) | Feature Request | Low | Paint Properties to include modifying linetype scales w... | Assigned | |
|
Task Description
Previous Feature Request #1285, dated 2015, incorporated in QCADPro 3.24. I regularly adjust linetype scales on hidden, centreline and phantom lines to achieve the best appearance on the drawing when printed. I note the Paint Properties feature copies all the attributes of the chosen line but does not copy the scale. I have to change the scale of each line, even after ‘painting’. This copying all Properties is something AutoCAD does. I know I could change the line to Hidden2 etc. and tick the ‘scale lines’ box in Drawing Properties but that is not always successful- copying properties is a quick and useful way of achieving the required result. QCAD Pro 3.24 Windows10.
|
|
2037 | QCAD (main) | Feature Request | Low | Support alternative angle reference | Assigned | |
|
Task Description
E.g. 0 degrees at the top, clock-wise for positive direction, alternative angle units.
|
|
2056 | QCAD (main) | Feature Request | Low | Option Duplicate layer (yy) inclusive all sub-layers. | Assigned | |
|
Task Description
If I’ve to duplicate a layer with a bunch of sub-layer it’s a kind of a Sisyphus task to get it done. Currently I have to duplicate each single layer. Then in an additional step I’ve to address each child layer to the proper parent layer.
Current lack: Marked parent layer with all sub-layer / Duplicate Layer / only ONE layer will be duplicated.
With other words: If I have to duplicate a layer with 5 sub-layer it requires 11 steps to get a copy of that tree ...
|
|
2226 | QCAD (main) | Feature Request | Very Low | macOS: support proxy icon | Assigned | |
|
Task Description
Support proxy icon in title bar. This can be used to move the file to another folder using drag and drop.
|
|
2227 | QCAD (main) | Feature Request | Low | CAM > CAM Export: post processor for tangential knife c... | Assigned | |
|
Task Description
See also: https://www.qcad.org/rsforum/viewtopic.php?f=2&t=8342
|
|
2229 | QCAD (main) | Feature Request | Low | Property Editor, option format property values as decim... | Assigned | |
|
Task Description
Angle Display is decimal although the decimal display is disabled in Application Preferences.
Format should be 17° 31’ 52” instead of 17.531111.
|
|
2233 | QCAD/CAM | Feature Request | Low | More selection options to select sheets for nesting | Assigned | |
|
Task Description
I’m often in the situation that I have to select for nesting 50+ sheets. Currently is only a Shift + left mouse click selection possible. It would be nice if QCAD/CAM could get for the nesting / sheet selection additional a mouse rectangle area selection.
|
|
2272 | QCAD (main) | Feature Request | Low | Support unit "US survey foot" | Assigned | |
|
Task Description
In the US, it is (unfortunately) still common to use US survey foot. It seems at least some DXF applications/libraries support this unit as a $INSUNITS value, some references:
There are two issues regarding this with QCAD:
If you open a document with $INSUNITS being 21, it’s reset to 0 (unitless/unspecified) when saved again, even when not changing anything.
It is not possible to select these units in the GUI.
I don’t know about standardization of these values, but my hope is that it’s at least possible to preserve the unit in an existing drawing. Given that this unit is supposed to be obsolete in some years, it might seem less important, but due to this transition, it might get even more important to be able to distinguish between units. Thanks!
|
|
2287 | QCAD (main) | Feature Request | Very Low | Evaluate draw order for preference "Prevent white-on-wh... | Assigned | |
|
Task Description
The Application Preference setting “Graphics View - Appearance - Prevent white-on-white/black-on-black display” seems to be a global setting that doesn’t take the draw order into account. For example: With the setting enabled, it prevents creating a white hatch of a higher draw order on top of a larger, colored hatch with lower draw order (background). The preference does not seem to evaluate if the object is truly drawn as “white-on-white”.
With the preference enabled, setting the object color as “white” will set the “white” color label, but the object color actually stays black. Its hard to determine why it happens in that case.
Is it possible to let the global preference setting be applied to objects after evaluation of the draw order, and determine if the object actually is a true case of white-on-white?
My workaround: Disable the preference setting (I think it is default = on), and only enable it for ad-hoc checks of hidden and overlooked objects.
|
|
2294 | QCAD (main) | Feature Request | Low | Auto Zoom with middle mouse button | Assigned | |
|
Task Description
I tried to assign double click on middle-mouse button to zoomauto command, but it seems it’s not possible currently.
Would love to see this feature.
|
|
2295 | QCAD (main) | Feature Request | Low | Deselect all with Escape key | Assigned | |
|
Task Description
I’m used to have persistant selection while drawing (Application Preferences > Graphics View:Appearance > Selection), but I’m missing deselection of all objects with ESC key. I have seen the option to deselect with right key, but it’s nice to have right key for context menu.
Currently ESC key cancels current active command, but would be nice if there is no command active to also deselect all features by default.
|
|
2296 | QCAD (main) | Feature Request | Low | Custom font type and size for command line widget | Assigned | |
|
Task Description
Would be nice to change default font type and size for command line widget.
|
|
2308 | QCAD (main) | Feature Request | Low | Viewport Scale Field | Assigned | |
|
Task Description
It would be helpful if the scale field that appears while placing a viewport would also re-appear when the viewport is selected after it’s already been placed in the layout. It would also be helpful if the pre-populated values in the dropdown matched those in the global layout scale field.
|
|
2331 | QCAD/CAM | Feature Request | Low | Tabs: Control over on which particular profile used. | Assigned | |
|
Task Description
Currently if I position one Tab (KT) to stacked profiles QCADCAM will use it on ALL in Z matching profiles. Practically in most cases would be to use tabs only on the lowest profile.
It would be nice to have some kind of control on which profile a tab has to be used.
|
|
2336 | QCAD (main) | Feature Request | Low | Add command to go back to previous nested block | Assigned | |
|
Task Description
“em” just always goes back to the main drawing. But for nested blocks, when jumping from edit mode of one block to the next nested block, it would be helpful to have some “ep” to go back to the previous block.
This was discussed at the forums...
|
|
2337 | QCAD (main) | Feature Request | Low | Distance information should be available in 2D and 3D | Assigned | |
|
Task Description
As per https://qcad.org/rsforum/viewtopic.php?f=32&t=9089, I suggest to extend the distance information tools:
* show Delta Z (at least when any of the elements has Z information) * allow switching between 2D and 3D distance * maybe allow to show both * maybe change the text to distinguish between them (”Distance” → “Distance 2D/3D”)
|
|
2339 | QCAD (main) | Feature Request | Low | Block List multible selection | Assigned | |
|
Task Description
It would be nice to have the possibility to select multiple blocks with Shift and/or CTRL + mouse like the Layer List to use a delete etc command on all selected blocks at once.
|
|
2340 | QCAD (main) | Feature Request | Low | Layer List / Block List: Link minus icon to keyboard de... | Assigned | |
|
Task Description
Referring to Layer List / Block List: It would improve the workflow if the Delete key on the keyboard would be linked to the minus icon (Delete). The command ER is also ignored in both list.
|
|
2378 | dwg2svg | Feature Request | Low | Export attributes on block references as namespaced XML... | Assigned | |
|
Task Description
dwg2svg supports exporting the layer name (and probably others?) as namespaced XML attributes (`qs:layer`) which works well. However I’d like to export block attributes as well, as seen on the following screenshot:
https://imgur.com/a/wUd0adE
(...so `ROOM_NAME` would become `qs:ROOM_NAME=”Eötvös terem”` on the respective XML element).
Thanks in advance.
|
|
2387 | QCAD (main) | Feature Request | Low | Open Drawings on Layout Block by Default | Assigned | |
|
Task Description
As the layout block contains the drawing sheet, the number, the viewports, it’s the presentable part of the drawing.
Maybe QCAD could be able to save on the dxf the “last state” of the drawing. If I saved on the Model and closed, it would open on Model... and if my last save was on the Layout”n”, it would open on Layout “n”.
At least on my work area, when opening a finished drawing, it’s the ideal for it to be opened in a Layout (if it was the active block while saving).
|
|
2398 | QCAD (main) | Feature Request | Low | Excessive Autosave | Assigned | |
|
Task Description
Autosave currently updates the backup file indefinitely regardless of whether the drawing has been modified since the last autosave. Request only update autosave following additional edits since last autosave.
|
|
2528 | QCAD (main) | Feature Request | Low | Add cycles (a.k.a. turns or revolutions) to the availab... | Assigned | |
|
Task Description
Hello, I recently bought QCAD Pro and this is my first Bugtracker report!
First, I want to say a big thank you for creating and maintaining such a wonderful software package!
I’ve never encountered a system for expressing constraints in 2D (or even 3D) that feels as natural, intuitive, and expressive as QCAD feels!
I am very grateful to have randomly found it somehow. I wish all user interfaces were designed this way and especially that vector art programs adopted similar constraint-based tools.
Anyway though, here’s the actual feature suggestion:
I noticed that QCAD is missing one especially convenient and naturally occuring angular unit: cycles (a.k.a. turns or revolutions).
I personally find cycles to be my favorite unit overall and to be the most intuitive to work with (when not needing to use physical protractors). I actually mostly work digitally and most of my uses for QCAD will be digital. QCAD is the only software I’ve found that really expresses 2D constraints the way I want to be able to work and lay things out.
Rather than redundantly belabor the many reasons why I think cycles should added to the available displayed angle units in the Preferences → Dimension Settings → Angular Dimensions dropdown list, I will simply link to the rather large discussion I’ve already had with Husky and CVH arguing my case about why I want it added and why many other users could benefit from it.
Here’s the link to the relevant forum discussion.
|
|
2529 | QCAD (main) | Feature Request | Low | Add normalized unit circle coordinates (complex numbers... | Assigned | |
|
Task Description
Similarly as for my previous suggestion submission, I also had a related idea for making it easier to work with complex numbers when using QCAD by adding normalized unit circle coordinates as another option in the Angular Dimensions display units options dropdown.
Here’s the corresponding forum thread I started.
|
|
2530 | QCAD (main) | Feature Request | Low | Make it possible to control the tooltip delay time when... | Assigned | |
|
Task Description
I noticed that every time I move my mouse from the main working canvas (schematic area) to the tool buttons on the left sidebar there is a delay before the first hover tooltip (which displays the tool names and hotkeys corresponding to each tool button) displays.
The tooltips remain fast (near instant) after that initial hover, but it it would be nice if there was an option field for controlling how long the tooltip delay is for that initial display delay.
Currently, on my Windows 10 machine, it takes about 1 full second for the tooltip to show, which may not sound like much but feels like a lot when trying to work faster.
Here is a link to the related forum discussion, which also discussed a different (and I’d say more useful/effective) idea as well.
I’m creating two separate Bugtracker submissions for that one thread though, to keep things clean.
Perhaps I should have created two separate forum thread for that to begin with.
|
|
2531 | QCAD (main) | Feature Request | Low | An always-visible hotkey overlay option would be extrem... | Assigned | |
|
Task Description
Hello! This is perhaps the most useful and valuable of the suggestion ideas I’ve had for QCAD so far!
I think it would be extremely useful if there was an option within the QCAD preferences for making it so that the hotkeys currently bound to each tool button in the UI (if existent) are always displayed such that they are overlaid on top of each of the buttons. There are two main approaches I can think of for doing that (both intended to avoid disturbing the existing layout of the UI):
Display the current hotkey binding associated by drawing it (probably in a distinct color) on one of the edges or corners of each of the buttons (such as the bottom middle side, the lower left corner, or the lower right corner). Even at a small font size I think this would be very effective and useful.
Instead of making the overlaid hotkey display in a small font at a side or corner of each button, you could have the hotkey text be in a large font and overlaid on top of the entire button, using things such as transparency and a distinctive (never used in the other parts of the UI) color to ensure that the button icons is still readable. A broader width of the font stroke may also help if transparency is used, so that the underlying icon lines remain more readable.
Both approaches have pros and cons. I personally lean towards the former, but Husky and CVH seemed to take issue with the readability of small fonts and so I later suggested the later option too.
They seemed opposed to both (at least during the forum discussion). However, I think this UI feature could be one of the best workflow speed improvements for the average user (many/most of whom probably don’t have time to memorize the hotkeys or just don’t end up doing so) of QCAD!
The gains in efficiency and pleasantness could be enormous potentially, even despite it QCAD already being among the most pleasant and well-designed programs I’ve ever used!
It is far faster to be able to instantly read a hotkey from the UI than to have to wait for a tooltip or to look the keystrokes up in the documentation.
Memorization is the fastest of course, but as someone who finds themselves constantly spread thin over many different programs (often half a dozen or more) for long spans of time I often find it difficult to remember all of the hotkeys for each program I use. Having such hotkeys always visible is useful for users who are spread thin, as many people increasingly in the world of software.
CVH suggested that I make custom icons myself, but doing so seems far worse than simply having QCAD automatically read and then print out the corresponding hotkeys over every tool in a programmatic and properly automated way.
I seriously think this would be one of the most awesome improvement you could ever add to QCAD!
Indeed, there is no missing feature I want more than this one!
Few programs do this but the few cases I’ve seen it the feature was extremely useful for speed without having to take weeks/months/years to fully memorize hotkeys only then forget them later. This idea eliminates that problem!
It would be glorious from a usability and accessibility standpoint! Please implement it!
Hopefully Qt’s GUI system is flexible enough to draw overlaid text over the buttons like this without to much hassle. That is the main potential impediment as I see it.
Anyway though, here is the associated forum discussion where I mentioned this idea. It was the same thread as the one where I also suggested adding a way to control tooltip delays.
|
|
2532 | QCAD (main) | Feature Request | Low | An "auto-tick" or "automated ruler creation" tool (adde... | Assigned | |
|
Task Description
Hey, this is the first of my feature suggestion submissions that isn’t tied to a corresponding suggestion thread on the QCAD forum.
Should I always create corresponding feature suggestion threads or is it ok (or better?) to just post ideas here?
Anyway though, here’s the idea:
I noticed that it is relatively easy to use things like the QCAD Split Entities and/or Paste Along Entity tool(s) to create an even set of divisions along a curve or line.
There’s also the Misc → Draw → Counter available too, for automated counting.
These together are useful for creating a “scale ruler” to be printed on a schematic for ease of reference or for use in cases where someone forgets to bring along a physical measuring device or when someone else is using that measuring device.
For example, one could print a to-scale 1 foot long ruler (or whatever other scale is relevant, e.g. 1 inch for small objects or just as a nice scale reference/legend/key) on the schematic page for convenience.
However, it would be nice if there was a convenient tool added to the Dimensions tool category that automated this entire process and was able to create arbitrary ruler-like numbered reference scales along lines (and even better if it also worked on arcs, though less important).
Even better would be if this “auto tick” or “auto ruler” tool supported multiple levels of tick scaling (e.g. 2 or 3) such as what one sees on actual rulers.
For example, an imperial ruler for a foot (I’m in the US currently) will typically having increasingly smaller tick marks added at halfway points between each of the numbered points along the ruler’s scale, which makes using it quickly much easier. For example, it’ll have a half-length tick for half an inch and then a quarter-length tick for each quarter of an inch within an inch (with the inch’s ticks being full length).
It seems like it could be relatively easy to implement that kind of nested tick marking system, which would make it super convenient and pleasant for the user of QCAD to create usable to-scale ruler-like objects wherever they desire them with hardly any effort!
I think this idea would also fit extremely well with existing tools in the Dimensions category and would be useful for many/most QCAD users!
It’s yet another good QCAD feature that could attract more people to buy upgraded copies of QCAD in the future I think!
I hope you implement it. Small conveniences still make a big difference.
Anyway, thanks a bunch again for creating this awesome program!
That’s all the suggestions I have for today.
I hope you have a wonderful weekend and upcoming week, etc!
|
|
2535 | QCAD (main) | Feature Request | Low | New tool idea: Scale polyline objects separately, each ... | Assigned | |
|
Task Description
In my current QCAD file I’m working on, I have a circular hub with a hole in it which I am also trying to place an alternating sequence of rectangular spokes of a certain relative size around.
I had 4 spokes that I had copied and rotated 45 degrees to create 8 spokes in total around the circle. I tried scaling the the non-cardinal spokes relative to the center of the circular ring, but that causes them to also move towards the center of the ring as they shrink, thereby putting them out of place as they scale.
I therefore had to activate the scale tool once per each object and set an origin (focus) point around the area where each spoke is “attached” to the ring in order to stop each from shifting inward to the circle as it scales.
It occurred to me though that there could be a simple tool or option to do this without that.
Each of my rectangles are polyline objects and thus are coherent continuous objects.
A new scaling tool could be designed such that it is based on simply clicking on each scaling origin on each object (using snapping tools if needed) and then clicking a check button (or enter) when done and then causing the scaling GUI to appear so the user can specify the desired scaling. Each scaling would then be applied to where the polylines were clicked instead of to all the objects as one.
This would be a much faster way to rescale a bunch of objects around individually varying relative scaling origins!
|
|
2537 | QCAD (main) | Feature Request | Low | More variants for converting element types could be use... | Assigned | |
|
Task Description
I don’t actually have any use for this idea currently, but am just posting it here to document it for consideration.
Basically, it occurred to me at least a few more useful conversions between shapes besides the existing ones could be useful.
For example:
Converting lines into axially aligned rectangles of a specified “radius” or “diameter” (with an option to delete or keep the original line geometry).
An option for the above (lines –> rectangles) that causes the intersections between the resulting rectangles to be automatically removed, like a kind of “automatic/magic wall creation tool” based on laying down lines instead of rectangles and then converting via this tool.
Converting circles/ellipses and rectangles back and forth between each other via their bounding volumes. It seems reasonably likely that people will sometimes want to convert circular design elements into rectangular ones and vice versa (e.g. deciding a rectangular column makes more sense than a cylindrical one and vice versa).
Converting any arbitrary selection into a corresponding bounding circle (not rectangle, which already exists) of sufficient size to enclose all points in the selection.
Basically, QCAD already has tools for converting shapes with operations that are a natural fit for the existing geometry, but has less tools for converting to entirely different geometry, but such uses could actually still be very useful potentially!
It seems likely to be common enough as a use case to merit inclusion, rather than just using scripting.
I don’t have any pressing need for these and I know that I could script them to create them if I really wanted to.
These are relatively minor ideas. I’m just putting this out here as more ideas for making this already wonderful software even better. :)
|
|
2063 | QCAD (main) | Performance Issue | Low | Bad performance while zooming inside layout block with ... | Assigned | |
2 |
Task Description
Zooming in and out is lagging to the point of unusable. This is happening in a layout block with the cursor pointing inside geometry with hatches. When the cursor is pointing outside the geometry zooming works as expected. The attached file has a very simplified testcase that shows this problem almost in the same way as a more complex drawing with multiple layers and hatches.
edit: I also attached the more complex drawing because it is a bit unclear to me where the lagging stops. Outside the viewport or outside the paper.
I just noticed the selection box has the same problem!
|
|
728 | QCAD (main) | Performance Issue | Low | Slow loading of drawing with many block inserts | Assigned | |
1 |
Task Description
Slow loading of drawing with huge number of block inserts (more than 10000).
|
|
1801 | QCAD (main) | Performance Issue | Low | low perfomance in paper space and viewports | Assigned | |
|
Task Description
Improving the performance of the exceptional use of the processors when switching from the model to the paper space (testing with the attached file) the functionalities of the commands for the viewports are too low in the paper space.
|
|
2021 | QCAD (main) | Performance Issue | Very Low | Cannot work with big dwg files | Assigned | |
|
Task Description
Openning a big file or doing any action in it, takes minutes to load. Even dragging the scrollbar slightly left or right, takes mintues to redraw the canvas again, which makes QCAD un-usable for professional use. Is there a way to make QCAD usable, after loading completed: - Like suppressing edit until user says so, - or taking snapshots of rendered canvases to another file and use it, as windows uses thumb.db ( for negative latency :P )
PS: I wish I could help a bit, but my hand are tied. I am just a java freak, I am opt to any idea of porting it to java, if she is still alive.
Tuğalsan Karabacak EEE, MSc Mobile Comp & App, IWE
|
|
1954 | QCAD/CAM | Release | Low | Revised PWM Post Processor | Assigned | |
|
Task Description
Hallo Andrew,
I have revised the PWM Post Processor to Revision D.
|
|
2242 | QCAD (main) | Suggestion | Low | Bill of Materials | Assigned | |
4 |
Task Description
It would be a very interesting feature to add to future versions.
I also use AutoCAD Mechanical 2012 and the BOM is synced with every balloon on the drawing. Making it easy to edit.
The core BOM accepts formula fields and we can easily calculate the mass of a part, with some Ifs and math.
The BOM that is shown in the actual drawing is more simplistic, and has just Part number, Quantity, Mass and the Description. But it’s related to the “core BOM”.
It’s a very interesting thing! It would be great on QCad.
|
|
1469 | QCAD (main) | Suggestion | Low | Cartouche automatique | Assigned | |
1 |
Task Description
Would not it be possible to create a kind of template for printing? We draw our room without cartridge. The cartridge will automatically appear when printed. The scaling could be automatic so that it goes in the A4 and therefore also will post the scale automatically. The name of the play could be the file name, date last saved after it the rest of the information that would be to add somehow (material index, designer, ...).
Original suggestion:
Bonjour,
Ne serait il pas possible de créer une sorte de template lors de l’impression ? On dessine notre pièce sans cartouche. Le cartouche s’affiche automatiquement lors de son impression. La mise à l’échelle pourrais être automatique pour que ca rentre dans le A4 et donc l’échelle s’afficherai aussi en automatique. Le nom de la pièce pourrais être le nom du fichier, la date du dernier enregistrement après c’est le reste des infos qui serait à ajouter je ne sais comment (matière, indice, dessinateur, ...).
|
|
1526 | QCAD (main) | Suggestion | Low | Exporting block attributes to CSV | Assigned | |
1 |
Task Description
Two useful commands make it necessary to
1-”delete all the history of the command lines without terminating QCad” ; and
2-”export attributes to the CSV file as exported to the Blocks List”
|
|
1789 | QCAD (main) | Suggestion | Low | Application Preferences / General / Performance :0 | Assigned | |
1 |
Task Description
Hi Andrew,
we know that you need to have always software performance in your mind to decide which features / tools can / should be implemented and on which way.
I really appreciate your effort to find the best middle way between software features and performance but I think also it’s a tough call to appraise worldwide the overall customer equipment to make the software workable to the best for everybody. That isn’t possible without compromise.
Maybe it would make sense to think about a new dialog in the “Application Preferences” to let the user decide what kind of feature are absolutely needed regarding to his/her work-task / equipment. I don’t mean that you need to cover every single thing but the main “performance jeopardy’s” should be covered with an on/off switch.
Yes I know - that isn’t done in 5 minutes but I think that can make your life easier in the long run and will cover even more customer.
Just my two cents. ;)
|
|
2138 | QCAD (main) | Suggestion | Very Low | Block zoomstate supersedes Model_Space after Undo of BC | Assigned | |
1 |
Task Description
Summary: Block zoomstate supersedes Model_Space after Undo of BC
QCAD Professional Version: 3.25.2.1 (3.25.2.1) Internet: QCAD.org Build Date: Oct 15 2020 Revision: 2895712 Qt Version: 5.13.2 Architecture: i386 Compiler: Unknown «< (Win installer 32 bit)
With the file provided: ZW to see the top green ‘revision cloud’ up close QQ Box select around the cloud »> 2 entities in selection BC, select origin somewhere inside the selection, accept proposed naming »> ‘Block 1’ is created from the selection TN BD, select the newly created Block Reference »> Auto zoom of ‘Block 1’ (Intended behavior) OO »> Returns to Model_Space with the zoomstate of the removed Block »> Halfway down the drawing »> The former zoomstate of the Model_Space is lost
Intended behavior is that the zoomstate of Model_Space and Blocks don’t mix See: https://www.qcad.org/rsforum/viewtopic.php?f=31&t=7797&p=30371#p30378
This proves they do, even if the block doesn’t exists anymore.
Regards, CVH
PS: 3th trial to enter a suggestion ...
|
|
2140 | QCAD (main) | Suggestion | Low | Changing navigation mode for mouse wheel doesn't change... | Assigned | |
1 |
Task Description
Looks like error, but may be that’s feature request.
CAD software uses typical navigation behavior as: Wheel = Zoom; Ctrl+Wheel = Scroll up/down; Shift+Wheel = Scroll left/right.
Any other software like browsers, office software (openoffice writer, ms excel and so on), 2d paint software like GIMP (Photoshop and so on) uses other behavior: Wheel = Scroll up/down; Ctrl+Wheel = Zoom; Shift+Wheel = Scroll left/right.
Users, that intensively use CAD and other software simultaneously prefer to make same behavior in their applications switching CAD scroll to plain mouse wheel.
QCAD’s “Application Preferences”: “Graphics View: Navigation”: “Mouse wheel/ two finger swipe”: “Scroll” allow user to assign scroll up/down to wheel mouse instead of Zoom. But there is mistake Ctrl+Wheel didn’t change to Zoom. Ctrl+Wheel continues to scroll up/down, as the wheel. Wheel = Scroll up/down; Ctrl+Wheel = Scroll up/down; Shift+Wheel = Scroll left/right. No zoom!
Draw manipulation at this mode like a hell: you need to use wheel in conjunction with Ctrl/Shift to point draw in desired position, than move your hand to +(-) for make desired zoom.
|
|
2146 | QCAD (main) | Suggestion | Very Low | Keep 'Invisible' objects invisible while saving | Assigned | |
1 |
Task Description
QCAD Professional Win installer 32bit Version: 3.25.2.4 (3.25.2.4) Internet: QCAD.org Build Date: Nov 18 2020 Revision: 40f4475 Qt Version: 5.13.2 Architecture: i386 Compiler: Unknown
Related topic: https://qcad.org/rsforum/viewtopic.php?f=33&t=7882 Explanation found in REntity.cpp Listed as a Public Member Functions inherited from RObject
Regards, CVH
|
|
2147 | QCAD (main) | Suggestion | Very Low | Allow breaking up self-intersecting a 2e time (at endpo... | Assigned | |
1 |
Task Description
QCAD Professional win installer 32bit Version: 3.25.2.4 (3.25.2.4) Internet: QCAD.org Build Date: Nov 18 2020 Revision: 40f4475 Qt Version:5.13.2 Architecture: i386 Compiler: Unknown
Continued from https://qcad.org/bugtracker/index.php?do=details&task_id=1757 Splitting the old report up ... Same file. In the left example one can cut (DI) once. Cutting the second segment results in NO cut.
Regards CVH
|
|
2148 | QCAD (main) | Suggestion | Very Low | Allow undo after breaking up self-intersecting with D2 ... | Assigned | |
1 |
Task Description
QCAD Professional win installer 32bit Version: 3.25.2.4 (3.25.2.4) Internet: QCAD.org Build Date: Nov 18 2020 Revision: 40f4475 Qt Version:5.13.2 Architecture: i386 Compiler: Unknown
Continued from https://qcad.org/bugtracker/index.php?do=details&task_id=1757 Splitting the old report up ... Same file. In the left example one can break out segment (D2): - removing one of the loops with the ‘remove’ option. - leaving both without the ‘remove’ option. Bug? Without the ‘remove’ option it can’t be undone.
Regards CVH
|
|
2149 | QCAD (main) | Suggestion | Very Low | Allow undo after auto trim self-intersecting with AX in... | Assigned | |
1 |
Task Description
QCAD Professional win installer 32bit Version: 3.25.2.4 (3.25.2.4) Internet: QCAD.org Build Date: Nov 18 2020 Revision: 40f4475 Qt Version:5.13.2 Architecture: i386 Compiler: Unknown
Continued from https://qcad.org/bugtracker/index.php?do=details&task_id=1757 Splitting the old report up ... Same file. In the left example one can auto trim (AX): - The lower loop. - The top loop. Bug? The action on the top loop can’t be undone.
Regards CVH
|
|
2162 | QCAD (main) | Suggestion | Low | Update the parameter with simplify of RPolylineData & R... | Assigned | |
1 |
Task Description
Unrelated to OS, nor version
Reported Jun 23, 2020 in: https://qcad.org/rsforum/viewtopic.php?f=30&t=7372
Status Dec 24, 2020: https://qcad.org/rsforum/viewtopic.php?f=30&t=7372#p30955 Documentation is updated. The Classes still refer to an ‘angleTolerance’.
Regards, CVH
|
|
2177 | Documentation | Suggestion | Low | Update class_r_polyline.html | Assigned | |
1 |
Task Description
Include RPolyline.getLeftRightOutline() method in class_r_polyline.html
In use since 11 Sept 2020
CVH
|