|
2556 | QCAD (main) | Bug Report | Low | Win11 Printing Orientation Issue: Landscape >>Portrait | Assigned | |
|
Task Description
Andrew,
Related topic: https://www.qcad.org/rsforum/viewtopic.php?f=33&t=10649
Already two different users report that Landscape is printed cropped in portrait format, both Win11. The behavior change occurred recently. Although the second user (rdtsc) reports the same behavior for latest Mabox Linux (Manjaro, Arch.)
Can not replicate that on Win7 32 bit nor on Win10 64 bit, both are no longer or not updated OS. For one, I have no orientation setting displayed in my printer dialog.
It seems not to be related to the QCAD version: Reported for: - Win11 QCAD Pro 3.29 - Win11 QCAD-CAM 3.27.8.0
Regards, CVH
|
|
1811 | QCAD (main) | Feature Request | Low | Zoom 1:1 | Assigned | |
2 |
Task Description
It would be nice to be able to adjust the zoom factor so that the scale on the screen matches a ruler which I lay on the screen.
Thanks!
|
|
2284 | QCAD (main) | Bug Report | Low | Zooming in & out causes grid/snap scale value change in... | Assigned | |
1 |
Task Description
I have set the grid/snap value to X=.0625 Y=.0625 on all 4 viewports. When zooming in and out the grid/snap scale changes from .0625 to 3.90625. at this point the grid/snap points differ, This causes a variation in the grid/snap reference points lending to drawing errors.
example When I use the grid settings defaults .01, when zooming in and out, the grid/snap scaling doesn’t seem to have this issue. Other values do, See below.
set value first zoom second zoom next zoom
point point point ...
0.01 0.1 1.0 10.0 ... 0.02 0.04 0.4 4.0 ... 0.04 0.16 1.6 16.0 ... 0.05 0.25 2.5 25.0 ... 0.0625 0.390625 3.90625 39.0625 ... 0.0254 0.64516 6.4516 64.516 ...
Why is there a squaring of the original set value? Which then becomes a new zoomed grid/snap value?
QCAD Professional Version: 3.26.4.0 (3.26.4) Internet: QCAD.org Build Date: Jun 3 2021 Revision: 0bb4334 Qt Version: 5.13.2 Architecture: i386 Compiler: Unknown
|
|
2495 | ECMAScript | Bug Report | Very Low | RLine.isParallel(RLine) may return true for certain non... | Assigned | |
1 |
Task Description
Andrew,
It took me a while to find the source of a certain freak bug I encountered. I used the RLine.isParallel(RLine) as a test for knowing if line segments were parallel or not.
Included below is script code that mimics the functionally of isParallel().
As far as I know isParallel() is nowhere used in the QCAD open source. Textual only found in RLine.cpp & .h or under: opennurbs, ecmaapi\generated and ecmagenerator\src.
// Example:
// RShape1: RLine(RShape(address: "0xcd70e28"), startPoint: "RVector(969.219858, -171.914894, 0.000000, 1)", endPoint: "RVector(1010.000000, -140.000000, 0.000000, 1)")
// RShape2: RLine(RShape(address: "0x7659770"), startPoint: "RVector(969.219858, -171.914894, 0.000000, 1)", endPoint: "RVector(930.000000, -340.000000, 0.000000, 1)")
----
var aShape1Angle = shape1.getAngle(); // =0.6640461628266838 rad
var aShape2Angle = shape2.getAngle(); // =4.483157047107694 rad
----
// RLine::isParallel(RLine) -> aTest1 || aTest2
var aTest1 = RMath.isSameDirection(aShape1Angle, aShape2Angle); // =false
var aTest2 = RMath.isSameDirection(aShape1Angle, aShape2Angle + Math.PI); // =true
var aTestOr = aTest1 || aTest2; // =>TRUE !?
----
// # BUG # RShape1 is considered as parallel with RShape2
----
// RMath::isSameDirection(dir1, dir2, tol) ... tol = RS.AngleTolerance = 1e-9
// for aTest1 -> ax1Test1 || ax1Test2
var ax1Dif = Math.abs(aShape1Angle - aShape2Angle); // =3.8191108842810104 rad
var ax1Test1 = ax1Dif < 1e-9; // =false
var ax1Test2 = ax1Dif > 2*Math.PI - 1e-9; // =false
var ax1TestOr = ax1Test1 || ax1Test2; // =>FALSE
----
// for aTest2 -> ax2Test1 || ax2Test2
var ax2Dif = Math.abs(aShape1Angle - (aShape2Angle + Math.PI)); // =6.9607035378708035 rad
var ax2Test1 = ax2Dif < 1e-9; // =false
var ax2Test2 = ax2Dif > 2*Math.PI - 1e-9; // =true
var ax1TestOr = ax1Test1 || ax1Test2; // =>TRUE
----
// # BUG # The second test of the second isSameDirection() test returns true because ax2Dif is over 2pi
Regards, CVH
|
|
1863 | ECMAScript | Feature Request | Low | WidgetFactory.saveState: save state of checkable QGroup... | Assigned | |
|
Task Description
QGroupBox widgets with <property name=”checkable”> are not saved in Qcad3.conf
|
|
2461 | dxflib | Bug Report | Very Low | ASCII Control characters not handled correctly in Commu... | Assigned | |
|
Task Description
I see the following problem: When I open a particular DXF file in the Professional Trial version 3.27.9.0 on macOS, “^I” in text fields is expanded to whitespace. When I open the same DXF file in the Community Edition 3.27.9.0 on NetBSD/x86_64 (installed from pkgsrc), “^I” in text fields is visible as “^I”.
|
|
976 | dxflib | Bug Report | Low | DXF import errors related to hatches, texts | Assigned | |
|
Task Description
See: http://www.qcad.org/rsforum/posting.php?mode=reply&f=30&t=2677
|
|
1203 | dxflib | Bug Report | Low | Images not saved (dxflib) | Assigned | |
|
Task Description
I am doing a bit of landscaping and using a (big) ortophoto as one of my layers in order to sanity-check on the ground measurements.
The layer contains a point and the image and nothing else.
The image is a 8MB file: “PNG image data, 4200 x 2980, 8-bit/color RGB, non-interlaced” and it is scaled to 210 coordinate units (meter) horizontally in the drawing.
With approx 50% probability the image disappears during Save, as see for instance in this diff of the DXF file:
@@ -158699,28 +153057,6 @@ AcDbXrecord
90
6
0
-IMAGEDEF
- 5
-A1
-100
-AcDbRasterImageDef
- 90
-0
- 1
-/critter/HTV10/Ortofoto/ortofoto201502f.png
- 10
-210.0
- 20
-149.0
- 11
-1.0
- 21
-1.0
-280
-1
-281
-0
- 0
ENDSEC
0
EOF
The point in the same layer does not similarly disappear, the bug only seems to affect images.
I have seen this bug from version 3.7.5.0 to git as of yesterday (63e06c778926a803bdfbffdf27b8c24d41511072).
I have not been able to correlate the bug with anything.
Looking closer at the DXF file (attached), there seems to be some residuce of attempts to insert images in protected/invisible layers, so this may be some kind of refcounting issue.
(Any chance of getting FreeBSD into the “Operating System” field ?)
|
|
1506 | dxflib | Feature Request | Low | writeVPort parameters | Assigned | |
|
Task Description
Add parameters to the function DL_Dxf::writeVPort. This way users will be able to specify the desired viewport.
Is the github the official repository? Are pull requests sent there accepted?
|
|
1542 | dwg2svg | Feature Request | Low | dwg2svg: add switch to show only given layer(s) | Assigned | |
|
Task Description
Implement a command line switch to only show a list of given layers for dwg2* command line tools.
|
|
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.
|
|
1824 | dwg2pdf | Feature Request | Low | dwg2pdf does not obey frozen layers in paper-space view... | Assigned | |
|
Task Description
We currently have a paper-space using two viewports with different layers from the model-space frozen. Unfortunately in the pdf output the layers which are frozen show up. dwg2pdf should obey the specific frozen layer for each viewport
|
|
1700 | dwg2pdf | Feature Request | Low | dwg2pdf: output multiple layouts | Assigned | |
|
Task Description
Add support to specify multiple blocks (layouts) to output (one per page).
|
|
1823 | dwg2pdf | Feature Request | Low | plotting error to pdf a Dwg where the view port is not ... | Assigned | |
|
Task Description
When trying to plot a dwg or a dxf to pdf where the viewport is orientated to a different angle than north up the data in the view port is plotted north up. see attached DWG and pdf for clarification.
|
|
1887 | dwg2bmp | Feature Request | Low | Add "-max-lineweight" option for dwg2bmp | Assigned | |
2 |
Task Description
Hi there,
A friendly request to add the option to set a maximum lineweight for raster conversions via dwg2bmp.
Depending on the LW configuration of the CAD file, rasterization operations sometimes yield terrible results (see attachment). This would also mirror the similar “-min-lineweight” options available on “dwg2svg” and “dwg2pdf” (although not on “dwg2bmp”).
See also: https://qcad.org/rsforum/viewtopic.php?f=32&t=6298
Thanks!
|
|
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
|
|
1888 | dwg2bmp | Feature Request | Low | Add support to disable hatch rendering on "dwg2bmp" | Assigned | |
1 |
Task Description
Hi!
A friendly request to add an option to disable hatch rendering on “dwg2bmp” conversions.
Depending on the nature of the conversion and the density of the hatch, this may render unintelligible images (see attachments). The option could look like “-t, -nohatch” to indicate hatches should be hidden before rendering. This could potentially become an option too for “dwg2svg” or “dwg2pdf.”
Amazing product, thank you so much!
|
|
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
|