|
1901 | QCAD/CAM | Feature Request | Low | CAM Traverse Toolpath | Assigned | |
|
Task Description
Hallo Andrew,
Still busy on the never ending G-code story. Urgently needed the very common Traverse Toolpath.
Example added as pdf.
Greetings
|
|
1902 | QCAD/CAM | Feature Request | Low | CAM G-Block Toolpath | Assigned | |
|
Task Description
Hallo Andrew,
Still busy on the never ending G-code story. Urgently needed the very handy G-code Block Toolpath. This ‘toolpath’ also solves a lot of “editing requests”.
|
|
1903 | QCAD (main) | Feature Request | Low | Saving layer settings, e.g. visibility status, associat... | Assigned | |
1 |
Task Description
In a medium complex drawing it may be too much details to have all layers in a drawing visible at once.
Instead a number of views would be created that saves not only zoom level and position but also what layers are visible and not (as appropriate for the purpose of that particular view). This is very cumbersome (to the extent it is not really realistic) to achieve today and requires a lot of duplication of both model and layers.
The advantage of adding this is the ability to have only one model (with multiple views) and avoid duplication of work and the risk of inconsistency inherent with many copies of the model.
As a further (and natural extension to this) would be the ability to used this functionality with view-ports to be able to create (possibly many) paper-spaces from a single model. This would however require view-ports to be aware of what view they are a window into. A single change in the model would then propagate to all defined view-ports and paper-spaces.
|
|
1904 | QCAD (main) | Bug Report | Very Low | File > Bitmap Export: Non-plottable layers not exported | Closed | |
|
Task Description
File > Bitmap Export does not export non-plottable layers.
See also:
https://www.qcad.org/rsforum/viewtopic.php?f=31&t=6364
|
|
1905 | QCAD (main) | Bug Report | Very Low | View > Property Editor: Changing attribute of block cha... | Assigned | |
|
Task Description
See also:
https://www.qcad.org/rsforum/viewtopic.php?f=33&t=6367#p23947
|
|
1906 | QCAD (main) | Bug Report | Low | Draw > Polyline > Polyline from Segments: Converting fu ... | Closed | |
|
Task Description
Win7/32bit
QCADpro 3.22.1.0
Full 360 degrees Arcs don’t convert correct to polylines with the methods OG and OC.
Both methods create a zero-length open type Polyline and remove the full Arc.
OG creates a Poly with 2 vertexes at the startpoint (= endpoint) and OC one with 0 (zero!) vertexes.
The firts one is selectable, the second one only with ‘Select All’//TA because there are no references.
The OL method with the same start and endpoint doens’t affect the full arc.
Neither a poly is created nor an error is generated that the method failed.
Typical the bulge of the OG method is (-)16331239353195370, the OC method has no references.
The math to calculate the bulge should result in a division by zero or an illegal function as tan(π/2).
Therefore a polyline can’t contain a 360 degrees arc by standard means.
From the OC method is known that it simplify coradial arc strings to a single arc.
This should not result in 360 degrees arcs what would result in zero-length segments.
(With CAM fuzzy things may happen at such positions)
Simplifying coradial arcs strings that would create a 360 degrees arc should result in no less then two coradial Arcs.
The OG method will then creates a open Poly with 3 vertexes, OC a closed one with 2 vertexes.
Found while fiddling around with editing CXF fonts.
CXF uses full Arcs, two half arcs and even polylines with coradial segments that forms circles are supported,
the OC closed polyline with 2 vertexes is recoded as two 180 degree Arcs (90-270&270-90).
Regards
CVH
|
|
1907 | QCAD/CAM | Bug Report | Low | having issues importing and opening dxf files | Closed | |
|
Task Description
can not import dxf files
|
|
1908 | dwg2maptiles | Bug Report | Low | dwg2maptiles: Transparent background not cleared | Closed | |
|
Task Description
See also:
https://www.qcad.org/rsforum/viewtopic.php?f=32&t=6389
|
|
1909 | QCAD (main) | Bug Report | Low | Blocks invisible when loading disappear when made visib ... | Closed | |
|
Task Description
See also:
https://www.qcad.org/rsforum/viewtopic.php?f=74&t=6377
Regression caused by fix to FS#1899 .
|
|
1910 | QCAD (main) | Suggestion | Low | Please take a look at 1898 again | Closed | |
|
Task Description
Please take a look at 1898 again. There is a problem.
|
|
1911 | QCAD/CAM | Feature Request | Low | Drill Toolpath | Assigned | |
|
Task Description
Hallo Andrew
It would be more than conveniant, defining the drilling locations of the drill toolpath, by selecting a circle’s center point.
|
|
1912 | QCAD/CAM | Bug Report | Low | Tool Description Error | Closed | |
|
Task Description
Hallo Andrew,
Testing the drill toolpath I find it hard to select the correct tool by a small bug
|
|
1913 | QCAD/CAM | Bug Report | Low | 3D Simulation Behaves odd | Assigned | |
|
Task Description
Hallo Andrew,
testing the drill toolpath I used single point markers.
In 3D simulation the tool drills the toolpath AND uses the drill as a mill.
Cam Export and generated G-code is not effected.
|
|
1914 | QCAD/CAM | Feature Request | Low | CAM layer On/Off | Closed | |
|
Task Description
Hallo Andrew
If CAM layer invisible do not 3D Simulate and do not write G-code.
|
|
1915 | QCAD (main) | Suggestion | Low | Viewport does not rotate view-port when changed in pape... | Assigned | |
|
Task Description
To reproduce
1. Select a new view-port in model-space
2. Select the appropriate paper-space
3. When the paper space opens change the angle of the viewport.
Actual
The object in the viewport changes but the viewport itself remains unchanged
Expected
That both the view-port and the object changes angle as the angle is updated
Motivation
If you abort the placement (but keep the angle) and go back to model-space and then redo the operation the view-port is rotated along the angle. It seems that the viewport only picks up the initial angle once the paper-space is open and ignores any changes thereafter
Workaround
1. Select the view-port per normal in model-space
2. Open the paper-space and set the wanted angle but do not place the view-port in paper space
3. Abort the placement on paper-space and redo the whole operation
Once the paper space is opened again the view-port will have the chosen angle
|
|
1916 | QCAD (main) | Bug Report | Low | Moving an object in an angled viewport with mouse does ... | Assigned | |
|
Task Description
To reproduce
1. Select a new view-port in model-space
2. Select the appropriate paper-space
3. When the paper space opens change the angle of the viewport to 90 degrees
4. Place view-port in paper space
5. Select the view-port in paper-space by clicking it
6. Try to move the object itself in the view-port (by clicking the “top” dot) to the right by moving the mouse to the right while holding the left mouse-button.
Actual
The object in the viewport moves down vertically NOT to the right
Expected
The object moves to the right
(It seems mouse movement does not compensate for the rotated angle of the viewport)
Workaround
None, except compensate for the angle in your head and moving the mouse the “wrong” way when correcting the placement of objects in the view-port
|
|
1917 | QCAD (main) | Feature Request | Low | Automatic labels with static information of the drawing | Assigned | |
|
Task Description
I would like static information of the drawing (like scale, creation-date, modified-date, revision etc) to be available as automatic labels to be placed in the drawing (with selectable style, font etc)
This would greatly simplify the creatin of title sections in the drawing and making sure it is consistent with the actual drawing and not requiring manual “synchronization”.
|
|
1918 | QCAD (main) | Bug Report | Low | Splines whit control points of order 1 and 4 not select ... | Closed | |
|
Task Description
Set up a spline with control points let’s say of the order 3.
Clone it 3 times with some offset in x&y.
Edit the degree property and set 1ste to 1, 2nd to 2, aso
Draw select partially from right to left.
Those of the order 1 and 4 aren’t selected.
Regards
|
|
1919 | QCAD (main) | Bug Report | Very Low | Wrong order XY(Z) for Ordinate Dimension in property ed ... | Closed | |
|
Task Description
Win7pro Qcad Pro 3.22.1.2
In property editor
properties of an Ordinate Dimension
Without Show Z
DefPoint is displayed in order YX?
With Show Z
Origin is displayed in order XZY?
DefPoint is displayed in order YZX?
LeaderEndPoint is displayed in order ZXY?
Regards
|
|
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
|
|
1921 | QCAD (main) | Feature Request | Very Low | Add error message when requesting raster for a non-exis ... | Closed | |
|
Task Description
(sorry for duplicate task, cannot remove it now)
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
|
|
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
|
|
1923 | QCAD (main) | Bug Report | Very Low | Faulty rendering Polylines with Global/Local Widths and... | Assigned | |
1 |
Task Description
Win7pro 32bit Qcad 3.23.0
Andrew,
The Arc segments of Polylines with Global or any Local Width render faulty where Global Z or any of the arc’s local Z is not zero.
In the attached drawing setting the Global Z of the inner poly to 5,10,...
The setting of Z to not zero affects the radius of the projected arc and not the bulging of the poly.
It also affects the projected widths of the line inversely, but not by changing the widths properties.
Pritty rare combination! True.
Qcad is 2D native! True.
Flatten will resolve this.
It is not a purely visual rendering fault, the poly will explode as such.
Maybe similar flaw as with uneven scaling blocks with arcs.
https://qcad.org/rsforum/viewtopic.php?f=8&t=5566#p20703
Regards
|
|
1924 | QCAD (main) | Bug Report | Low | SweepAngle = 0 | Closed | |
|
Task Description
Win7pro 32bit Wininstaller Qcadpro 3.23.0
Draw an arc.
Select the arc.
In Property Editor:
Set start angle to 135
Set end angle to 135
SweepAngle = */-360
edit the end angle and add “+360”, hit enter
SweepAngle = 0
An arc with zero sweep is a point.
A point is not an arc.
With the same start and end parameter an arc should have a sweep of +/-360.
As for entries by points or by angles.
Regards
|
|
1925 | QCAD (main) | Suggestion | Low | Poly Ref Points manipulation that generates null-segmen ... | Closed | |
|
Task Description
Win7pro 32bit Wininstaller Qcadpro 3.23.0
With a polyline.
Select the poly.
Pick any reference point of a vertex.
Place it on any of its neighboring vertex reference points.
A null-segment is created.
The placement can not be undone by re-picking the reference point.
Can be Undone/Redone.
The action can result from editing the vertex coordinates.
When exploding null-entities are created.
This action should delete:
- if the target is next: the picked vertex. (incl. start or end-1)
- if the target is prior: the targetted vertex. (incl. start or end-1)
- if the target is and next and prior: both the prior and the picked vertex.
As the user intentionally places any vertex reference points on:
- any excluding its neighbors:
→ the intented nature is ‘Self-Touching’, ‘Self-Crossing’ or ‘Trace-Back’.
- any of its neighbors:
→ the intention is to delete the segment(s).
Regards
|
|
1926 | QCAD (main) | Feature Request | Low | No negative coordinate values ? (DO command) | Assigned | |
1 |
Task Description
Just starting with QCAD, for some hours now - really excellent user interface (compared to other low budget CADs, like DCAD, or BeckerCAD...) !
Surprisingly, point coordinates - entered via the command line, and shown with correct positions on the drawing- are not displayed correctly with the ‘dimordinate’ (DO) command.
There are no negative values, even when the center point (0;0) is right in the middle of the drawing, so points left and below should have !
GW.G
|
|
1927 | QCAD (main) | Bug Report | Low | Drawing and printing inconsistent, with wrong/missing e ... | Closed | |
1 |
Task Description
Drawing and PrintPreview are consistent, but printout differs : rectangle missing (bottom right), line missing (bottom green line) - see att. Error can be reproduced, after saves and restores.
A VERY elementary WYSIWIG-problem....
|
|
1928 | QCAD (main) | Feature Request | Low | Optionnally 'Auto clean up' after generation of NaN / N... | Assigned | |
1 |
Task Description
Some functions / methods can generate some sort off entity or part with NaN / Null / Null-lenght ... props.
Some explicitly don’t and test their actions with isNull().
As these serve a purpose in some processes, trails of them can be part of the results.
For some users Null / Null-lenght are meaningfull, for other users these produce errors down the line.
In a few cases its a desirable feature eg. controlpoint spline.
(Allthough there are no Null props involved with equal successively controlpoints)
Many problem post on the forum are related to Null - Zero and so on.
In some cases it can’t be undone by re-editing the drawing.
https://qcad.org/bugtracker/index.php?do=details&task_id=1925
If it can’t be undone by Undo/Redo it is a bug.
https://qcad.org/bugtracker/index.php?do=details&task_id=1757
In some cases there is a difference noticed after file save-close-open.
|
|
1929 | QCAD (main) | Bug Report | Medium | Printing Problem - Preview differs from Printout | Closed | |
|
Task Description
... ? I reported this already some days ago, but the task doesn’t show up in the list? ...
Comparing ‘Drawing’ and ‘Preview’ - o.k.
Comparing ‘Preview’ and ‘Printout’ - NOT o.k. ! Elements are missing
(Rem: in the QCAD sketch itself, the missing elements are in a separate layer; however, anyway - preview should show the same image as the printout !?)
G.W.
|
|
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?
|
|
1931 | QCAD (main) | Bug Report | Low | File > SVG Export: hatch arc interpolation | Closed | |
|
Task Description
Hatches with arc boundaries are exported as crude polygons.
See also:
https://qcad.org/rsforum/viewtopic.php?f=33&t=6494
|
|
1932 | QCAD (main) | Bug Report | Very Low | Check for update fails to discover new version | Closed | |
|
Task Description
“Help→Check for QCAD Pro Updates” fails to discover new version. Tested on OSX and Linux versions.
|
|
1933 | QCAD (main) | Bug Report | Low | File > Advanced SVG export: file overwrite check doesn' ... | Closed | |
|
Task Description
In the Advance SVG Export dialog, when I edit the filename to be different than the default file that already exists and then clear the checkbox for “Overwrite existing file without asking” just to make sure that I haven’t already created a file with the modified name as well, then I get a popup warning that the export would overwrite the default filename, not the name as edited. In other words, the overwrite check ignored the fact that I edited the filename.
Observed on MacOS Mojave (10.14), but probably applies to all.
|
|
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
|
|
1935 | QCAD (main) | Bug Report | Low | Startup preferences | Closed | |
|
Task Description
Startup preferences
On Mac 10.14.6: QCAD Pro → Preferences... → Startup
Check or uncheck “Enable Splash Screen”
1. Restart of QCAD, the splash screen with Initialising add-ons xx% is identical
2. Apply, Cancel and OK buttons - why have both Apply and OK buttons?
|
|
1936 | QCAD (main) | Bug Report | Low | ver 3.23 not saving font information | Closed | |
|
Task Description
The attached file is not saving font preference.
All fonts on the online layer are reported as the standard font. If I highlight one or all of the text entities and change the font to something like Yu gothic light, the property page reports yu gothic light and the screen reflects the changed font.
If I save, close and reload, the fonts for all text is again “standard”.
So then I try to enter new text via the “A” draw text command icon. I select “Broadway.ttf” as the main font in the text entry dialog.
One word “Broadway” is entered as the text. it appears on the upper left of the screen as expected and the font name is Broadway in the property editor. If I look at the dxf file source there is a whole bunch of text styles.
I save and close the file, and then open it again. Now the word Broadway has changed to font name “standard” in the property editor and is very definitely not the Broadway.ttf font.
I am not the originator of the file, I am just trying to change the font. If I start a new file and enter new text the font saves just fine, so I am thinking it is a setting somewhere, but I am unable to find it.
We (me and my customers) use these files for engraving so exact font is critical.
|
|
1937 | QCAD (main) | Bug Report | Low | Circle shown in QCAD but not in AutoCAD | Closed | |
|
Task Description
The attached drawing shows two large concentric circles when viewed in QCAD but the inner circle is missing when viewed in other CAD programmes. This cost $50 in rework as my laser cutting was not cut correctly!
|
|
1938 | QCAD (main) | Bug Report | Medium | Segfault when trying to insert block from library (Fedo ... | Closed | |
|
Task Description
(base) [kforrester@FedoraWorkStation qcad-3.23.0-pro-linux-x86_64]$ ./qcad
QCAD version 3.23.0
10:21:34: Debug: calling odInitialize
10:21:34: Debug: dropped global XDATA (no res buf): “ViewportCenter” 10:21:52: Debug: importing file: /home/kforrester/Resilio Sync/Technical/Process Engineering/equipment_tag_and_name.dxf
./qcad: line 9: 3844 Segmentation fault (core dumped) LD_LIBRARY_PATH=”$DIR” “$binary” “$@”
QCAD has unexpectedly quit.
Please use the offscreen platform plugin for headless systems
(without a running X11 server):
./qcad -platform offscreen
In addition, you might have to override the default Qt style
to prevent the loading of a native desktop style (such as GTK):
./qcad -style plastique
I have tested this in version 3.22.1 too and get the same result. Reverting all the way back to 3.13.1 results in an operable version of qcad when working on the same file and library blocks.
|
|
1939 | QCAD Community Edition | Bug Report | Low | Right click not working in QCAD Community Edition | Closed | |
1 |
Task Description
After I remove the .dll files from the pro trial version, right click stop working on Windows 10.
I went a little further to try identifying which of the 5 files specifically causes right click to stop working, and I found that it is qcadproscripts.dll. The presence or absence of the other 4 dll files that make up the pro version has no influence on this behavior.
|
|
1940 | QCAD/CAM | Feature Request | Low | CAM > CAM Configuration: Add program description | Assigned | |
1 |
Task Description
Add a program description to the CAM configuration dialog and export to postprocessors as variable.
See also:
https://www.qcad.org/rsforum/posting.php?mode=quote&f=32&p=24649
|
|
1941 | Snapshot Release | Bug Report | Low | Invisible layers displayed | Closed | |
|
Task Description
Snapshot release 3.23.0.2
See also:
https://qcad.org/rsforum/viewtopic.php?p=24757
|
|
1942 | QCAD (main) | Bug Report | Low | Draw > Circle > Two tangents and point: fails for case ... | Closed | |
|
Task Description
The result of the tool CT2 depends on the position where the circle is constructed.
See also https://www.qcad.org/rsforum/viewtopic.php?f=32&t=6577&p=24772#p24772
|
|
1943 | QCAD (main) | Bug Report | Low | Tool "New from Template" fails | Closed | |
|
Task Description
QCAD 3.23.0.2
File / New from Template fails in different situation like immediately after launching the tool, sometimes after changing directories in the dialog like from imperial to metric etc..
QCAD tries for ever (wait cursor) or even quits QCAD. It’s not a clear pattern ...
See also:
https://www.qcad.org/rsforum/viewtopic.php?f=89&t=6585
3.23.0.2 doesn’t works
3.23.0 works
Reported on Ubuntu 19.4, Win10
|
|
1944 | QCAD (main) | Bug Report | Low | Block toggle switch for visibility fails | Closed | |
|
Task Description
3.23.02 Block toggle switch for visibility fails.
3.23.0 Block toggle switch for visibility works.
|
|
1945 | QCAD (main) | Bug Report | Low | Splines saved incorrectly | Closed | |
|
Task Description
Closed splines (Control points) are saved as “not closed” with a new knot (when DXF is closed and re-opened).
Is this behavious intended ?
|
|
1946 | QCAD/CAM | Bug Report | Low | CAM > Cam Legacy Export: Cut inner paths before outer p ... | Closed | |
|
Task Description
The option “Cut inner paths before outer paths” is ignored, causing trouble when outer paths are cut first.
Attached is a link to the script files and gcode examples.
|
|
1947 | QCAD (main) | Bug Report | Low | Startup failure | Closed | |
|
Task Description
QCAD community, Git ba68e28d3d (current HEAD), fresh clean compile on Ubuntu 18.04/x64 (gcc 7.4.0, Qt 5.9.5)
QCAD version 3.23.0.2
Warning: QApplication: invalid style override passed, ignoring it.
Warning: Qt WebEngine seems to be initialized from a plugin. Please set Qt::AA_ShareOpenGLContexts using QCoreApplication::setAttribute before constructing QGuiApplication.
Warning: action not found: "Scheme"
Warning: RScriptHandlerEcma::eval: script engine exception: "TypeError: Result of expression 'RS.getIdealThreadCount' [undefined] is not a function."
Warning: "<anonymous>(uiFile = 'scripts/Widgets/ViewportWidget/ViewportWidgetQt.ui', graphicsSceneClass = undefined) at /home/ice/w/qcad/qcad/scripts/Widgets/ViewportWidget/ViewportWidget.js:172\n<anonymous>(viewports = [object Object], uiFile = undefined, graphicsSceneClass = undefined) at /home/ice/w/qcad/qcad/scripts/Widgets/ViewportWidget/ViewportWidget.js:75\n<anonymous>() at /home/ice/w/qcad/qcad/scripts/File/OpenFile/../NewFile/NewFile.js:248\n<anonymous>() at /home/ice/w/qcad/qcad/scripts/File/OpenFile/../NewFile/NewFile.js:109\n<eval>() at 1\nslotTrigger() at -1\nopenFiles(args = , createNew = true) at scripts/autostart.js:209\nmain() at scripts/autostart.js:796\n<global>() at scripts/autostart.js:834"
Warning: RScriptHandlerEcma::eval: script engine exception: "TypeError: Result of expression 'RS.getIdealThreadCount' [undefined] is not a function."
Warning: "<anonymous>(uiFile = 'scripts/Widgets/ViewportWidget/ViewportWidgetQt.ui', graphicsSceneClass = undefined) at /home/ice/w/qcad/qcad/scripts/Widgets/ViewportWidget/ViewportWidget.js:172\n<anonymous>(viewports = [object Object], uiFile = undefined, graphicsSceneClass = undefined) at /home/ice/w/qcad/qcad/scripts/Widgets/ViewportWidget/ViewportWidget.js:75\n<anonymous>() at /home/ice/w/qcad/qcad/scripts/File/OpenFile/../NewFile/NewFile.js:248\n<anonymous>() at /home/ice/w/qcad/qcad/scripts/File/OpenFile/../NewFile/NewFile.js:109\n<eval>() at 1\nslotTrigger() at -1\nopenFiles(args = , createNew = true) at scripts/autostart.js:209\nmain() at scripts/autostart.js:796\n<global>() at scripts/autostart.js:834"
Warning: At least one uncaught exception:
Warning: "<anonymous>(uiFile = 'scripts/Widgets/ViewportWidget/ViewportWidgetQt.ui', graphicsSceneClass = undefined) at /home/ice/w/qcad/qcad/scripts/Widgets/ViewportWidget/ViewportWidget.js:172\n<anonymous>(viewports = [object Object], uiFile = undefined, graphicsSceneClass = undefined) at /home/ice/w/qcad/qcad/scripts/Widgets/ViewportWidget/ViewportWidget.js:75\n<anonymous>() at /home/ice/w/qcad/qcad/scripts/File/OpenFile/../NewFile/NewFile.js:248\n<anonymous>() at /home/ice/w/qcad/qcad/scripts/File/OpenFile/../NewFile/NewFile.js:109\n<eval>() at 1\nslotTrigger() at -1\nopenFiles(args = , createNew = true) at scripts/autostart.js:209\nmain() at scripts/autostart.js:796\n<global>() at scripts/autostart.js:834"
17:14:39: Debug: "<global>() at 172"
Then QCAD exits (does not start). As far as I remember, 3.23.0.2 release was fine.
|
|
1948 | QCAD (main) | Bug Report | Low | Modify > Offset (through Point): Point orthogonal to en ... | Closed | |
|
Task Description
See also:
https://www.ribbonsoft.com/rsforum/viewtopic.php?t=6590
|
|
1949 | QCAD (main) | Bug Report | Low | Modify > Break out: Leftover (zero length line) after u ... | Closed | |
|
Task Description
When using D2 on the vertical line (orange line in the attached example) a small zero length line is left over. This doesn’t happen if the vertical orangle line were a finite, line with two distinct endpoints.
|
|
1950 | QCAD (main) | Bug Report | Low | File > Save As: File dialog offers unsupported export f ... | Closed | |
|
Task Description
QCAD Pro fails to write R10, R9, R2.6, R2.5 dwg files. Younger types and dxf work as expected.
Tested the issue back to QCAD 3.18 - no version is able to save those file types.
See also:
https://www.qcad.org/rsforum/viewtopic.php?f=33&t=6620&p=24980#p24980
|
