|
1919 | QCAD Bugtracker | QCAD (main) | Bug Report | Very Low | Wrong order XY(Z) for Ordinate Dimension in property ed ... | Closed | | CVH |
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
|
|
2556 | QCAD Bugtracker | QCAD (main) | Bug Report | Low | Win11 Printing Orientation Issue: Landscape >>Portrait | Assigned | | CVH |
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
|
|
2538 | QCAD Bugtracker | QCAD (main) | Bug Report | Very Low | Weight 2.11 French translation typo | Assigned | 1 | CVH |
Task Description
Andrew,
When switched to French I detected a typo in the drop down box for Lineweight.
Weight 2.11mm is listed as 1.58mm {2.11m?} https://github.com/qcad/qcad/blob/master/ts/qcadcore_fr.ts#L1228-L1229 Also see attached image file.
May I ask why only ISO types have a comma instead of a point in French. The use of a comma is uncommon in the Property Editor even when that is the native decimal separator. I also detect an extra space between the value and ‘mm’ and that only for the ISO types.
This only occurs in: https://github.com/qcad/qcad/blob/master/ts/qcadcore_fr.ts https://github.com/qcad/qcad/blob/master/ts/qcadcore_pl.ts https://github.com/qcad/qcad/blob/master/ts/qcadcore_pt.ts
Probably not OS or QCAD version related.
Regards, CVH
|
|
2151 | QCAD Bugtracker | QCAD (main) | Bug Report | Very Low | Update viewport on Layout after Layer property change | Closed | 1 | CVH |
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
With the attached file: Viewing Layout1 Changing ON/OFF or Frozen state of layers in the Layer List
The view doesn’t update immediate. Selecting an entity: Yes After QQ Yes Switching to another Application and reverting the focus back to QCAD: Yes Using zoom / pan or the Zoom functions: No Changing the display modes: Yes Starting an action: No
|
|
2162 | QCAD Bugtracker | QCAD (main) | Suggestion | Low | Update the parameter with simplify of RPolylineData & R... | Assigned | 1 | CVH |
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
|
|
2219 | QCAD Bugtracker | ECMAScript | Task | Very Low | Update simple_create.js addSimpleText() | Closed | 1 | CVH |
Task Description
Andrew,
Reading: https://www.qcad.org/rsforum/viewtopic.php?&t=8286
Can you update addSimpleText() as Text.Width is fixed =100
What is the noTextWidth value?
As far as I can detect ... PrintPreviewImplPro.prototype.addDecorations uses value 1. CrankWheel.js uses value 1. ExText.prototype.beginEvent uses value 2. ExDrawFonts.prototype.beginEvent uses value 1. Counter.prototype.getOperation uses QCAD.ini or default zero. TextAlong.prototype.getTextData usses the width of the textData from the dialog.
Regards, CVH
|
|
2177 | QCAD Bugtracker | Documentation | Suggestion | Low | Update class_r_polyline.html | Assigned | 1 | CVH |
Task Description
Include RPolyline.getLeftRightOutline() method in class_r_polyline.html
In use since 11 Sept 2020
CVH
|
|
1648 | QCAD Bugtracker | QCAD (main) | Feature Request | Low | Uniform Layer listing in dropdown as in Layer List Widg ... | Closed | 1 | CVH |
Task Description
The order layers are listed in dropdown boxes is different as how there are presented in the Layer List Widget. Uniformity can shorten lookup time drastically with a large number of layers / sublayers.
|
|
2141 | QCAD Bugtracker | ECMAScript | Suggestion | Low | Typo in simple.js | Closed | | CVH |
Task Description
Andrew,
Both disableInput() & enableInput() in simple.js state that input is prevented ...
It is most obvious
Regards, CVH
|
|
1750 | QCAD Bugtracker | QCAD (main) | Bug Report | Medium | trimming polylines | Closed | | CVH |
Task Description
Trimming polylines especialy those with a string of small segments should be done at the intersection of those polylines. Now trimming is done with the seggments that where the nearest when selecting the two polylines.
|
|
1983 | QCAD Bugtracker | QCAD (main) | Feature Request | Low | Trim All or Bulk Break out | Assigned | 4 | CVH |
Task Description
This is a trim method I am missing in Qcad.
20 years ago it existed in CadKey. You had a bunch of lines or segments. You defined a (new) line or segment as cutter. ‘Trim All’. You pointed at the side of the cutter entity to trim all intersecting at that side.
Pritty the same as in this topic: https://qcad.org/rsforum/viewtopic.php?t=5221
Only in rare cases I can use Husky’s workaround as pro. It all depends on what else is in the clipping rectangle that is needed to trim all intended. If of no use all single crossing entities have to be chosen one by one.
Regards, CVH
|
|
2179 | QCAD Bugtracker | QCAD (main) | Bug Report | High | The use of 'Edit Block In-place' corrupts other open fi ... | Closed | | CVH |
Task Description
QCAD Professional Win7 winInstaller 32bit Version: 3.25.2.7 (3.25.2.7) Internet: QCAD.org Build Date: Dec 16 2020 Revision: e06f230 Qt Version: 5.13.2 Architecture: i386 Compiler: Unknown
Include file was open when using ‘Edit Block In-place (BB)’ in an other drawing. Happend on 5/1/2021 just before 2:56 am https://qcad.org/rsforum/viewtopic.php?&t=7945#p31055
‘Edit Block In-place (BB)’ is never used in this drawing. There was never a Block in this file. I might have switched focus.
Re-installed QCAD a dozen times meanwhile. Wiped all what remained of QCAD twice. Cleaned up the windows registry twice. Lastly left out all kinds of my custom scripts. Simply a bare install with the msi file.
How to replicate: - Start QCAD in normal mode - Load included file - Set App.Prefs .. Startup .. Restore open files - Close QCAD - Start QCAD in debugger mode (-rescan -enable-script-debugger -always-load-scripts)
Boot fails. Every successive trial.
When booting in normal mode I see the BB options toolbar blink shortly.
3 Screengrabs in DebuggerModeError.zip in the same topic. The blink I can’t catch.
I can Boot with no file to retore on open in debugger mode and load the file. I have several of those files, all were open that day at 2:56 am
CVH
|
|
1924 | QCAD Bugtracker | QCAD (main) | Bug Report | Low | SweepAngle = 0 | Closed | | CVH |
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
|
|
2180 | QCAD Bugtracker | QCAD (main) | Feature Request | Very Low | Surface area off a hatch | Closed | 1 | CVH |
Task Description
That would ease this task: https://www.qcad.org/rsforum/viewtopic.php?f=32&t=8000
Correct surface area included. CVH
|
|
2178 | QCAD Bugtracker | QCAD (main) | Bug Report | Low | Stored Color of text dimension changes | Assigned | 1 | CVH |
Task Description
QCAD Pro 3.25.2.7 Win7 Wininstaller 32bit Related Topic: https://www.qcad.org/rsforum/viewtopic.php?&t=7954
Reported is that black is saved as #00004c (dark blue) Radek (iMac (Retina 5K, 27-inch, 2017), Catalina 10.15.7 (19H114)
My system/installation saves black as #4c000 (dark red)
When using single primary colors these get reduced to #4c, #7f, #99, #cc & #ff. The threshold for that are #00, #65, #8b, #b2 & #e5 See: DimColorScale (png & dxf)
8 standard CAD colors fail saving correct Black (something with #4c) Dark Red, Dark Green, Dark Blue, Dark Cyan, Dark Magenta, Dark Yellow (#80 turns #7f) & Gray (#adadad instead of #a0a0a4)
As with Gray, when mixing the 3 colors it gets rather fuzzy ... #505050 & #555555 both turn #5b5b5b & #464646 turns #4c4226
A snippet of my investigation is included in the topic (45 files in a ZIP)
CVH
|
|
1802 | QCAD Bugtracker | QCAD (main) | Bug Report | Low | Startpoint indication disapears for some entities while ... | Closed | | CVH |
Task Description
Having a multi selection and at least one ‘older’ arc the startpoint indication in red of some entities might disappear.
Entities that suffer from this are: Other arcs Polyline Splines
Only the ‘oldest’ arc in selection will have a startpoit indication. Multi selection of ‘newer’ entities from the list above will not if an ‘older’ arc is part of the selection. Deselecting de ‘older’ arcs will reveal the startpoints up to the ‘oldest’ arc.
In the file provided entities where drew in order from left to right. Select all and start deseleting arcs from the left.
The behaviour is affected by changing the draw order property and a save/close/open. In the second file the rightmost arc was set to draw order 7, the same as the 4th was. After save/close/open it is renumbered to 8 and the behaviour is different as in the firts file.
Regards
|
|
1918 | QCAD Bugtracker | QCAD (main) | Bug Report | Low | Splines whit control points of order 1 and 4 not select ... | Closed | | CVH |
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
|
|
2275 | QCAD Bugtracker | QCAD (main) | Bug Report | Low | Snap > Center: snapping to center of polyline arc segme ... | Closed | | CVH |
Task Description
QCAD Professional Win7Pro WinInstaller Version: 3.26.4.5 (3.26.4.5) Internet: QCAD.org Build Date: Jul 20 2021 Revision: e596276 Qt Version: 5.13.2 Architecture: i386 Compiler: Unknown
See attached file: - The 9 center snapping points of the 24 bulging segments are all presumed to be incorrect - For some segments the center snap is outside the arc shape from a bulging segment - For some segments there are 2 solutions
Regards, CVH
|
|
2438 | QCAD Bugtracker | ECMAScript | Bug Report | Low | simple_modify.js > Faulty parameter explanation docDest ... | Closed | 1 | CVH |
Task Description
Andrew,
simple_modify.js function paste() 10 * \param docDestination RDocument to paste into (or undefined for current document)
A) This should be a document interface of the type RDocumentInterface. B) The function uses the parameter diDestination and not docDestination
https://www.qcad.org/rsforum/viewtopic.php?f=30&t=9742
Regards, CVH
|
|
1763 | QCAD Bugtracker | QCAD (main) | Feature Request | Low | Simple Modify Move function | Closed | | CVH |
Task Description
Moving things require an extra click on ‘Delete original’ and a click on ‘OK’
A simple Modify Move functionality will reduce mouseclicks for moving by 2 for every move that is made.
Regards
|
|
1760 | QCAD Bugtracker | QCAD (main) | Bug Report | Very Low | Self-crossing polylines can't be cut twice at segment c ... | Closed | | CVH |
Task Description
Re-entering dividing problem from FS#1757
Divide the poly selecting near segment 1 at the segment crossing. > A new node is inserted on the crossing and made start and end node. Divide the poly again selecting near segment 2 at the segment crossing. > no division appears to be done.
One can’t divide the second segment at the crossing
Presumed intended behaviour like FS#1750
Regards
|
|
1755 | QCAD Bugtracker | QCAD (main) | Feature Request | Low | Selecting standard rotation angles by mouse click for M... | Assigned | 1 | CVH |
Task Description
This would be nice. It will save a lot mouse - keypad changes for me.
|
|
1606 | QCAD Bugtracker | QCAD (main) | Performance Issue | Low | Selecting 'Draw Order' halts system temporary | Closed | | CVH |
Task Description
Merely clicking on ‘Draw Order’, and usualy unintended, halts the system for several seconds up to several tens of seconds.
Intel(R) Core(TM) i7-2600K CPU @ 3.40Ghz 4,00 GB RAM installed 3,49 GB usable 32-bit Operating System Windows 7 Professional SP1
|
|
2258 | QCAD Bugtracker | QCAD (main) | Bug Report | Low | Selected entities send to an 'Off' layer retain their s ... | Closed | | CVH |
Task Description
Andrew,
Seen in al previous versions that I know of. To recreate and merely as an example: With: - A polyline entity on a layer ‘polyline’ (notLocked - notFrozen - Visible) - A hidden layer ‘exploded’ (notLocked - notFrozen - notVisible)
- Select the polyline .. DP .. XP » duplicated polyline explosion in selection. - Set the selection its layer to ‘exploded’ by a double click in the Layer List or by Property Editor. - Hide layer ‘polyline’ by toggling its visibility. - Unhide layer ‘exploded’ by toggling its visibility.
The explosion is still in a dark red color. Workaround: TA & TN
Regards, CVH
|
|
2385 | QCAD Bugtracker | QCAD (main) | Bug Report | Low | ScriptItems are inserted with the unit setting for a ne ... | Closed | | CVH |
Task Description
Tested on a Win7 32bit and a Win10 64bit system.
With App.Prefs defaults for new drawings set to mm, mm, metric. Inserting a ‘CubeCuttingOut’ with the default size 10 into a drawing in inch results in size 0.39370079” what is indeed 10mm.
One would expect it to be sized 10 units of the target drawing.
Recently reported by Husky concerning the QCAD Utilities by MikeJ. https://qcad.org/rsforum/viewtopic.php?f=30&t=9429&start=15#p38045
ScriptItems are first created on a new (offline) document. QCAD will then adapt the size with unit conversion. Then it will scale, rotate, flip according the ‘Insert Script’ tool options.
This is fully predictable for standard library items where the source is a dxf file with a defined unit and no unit conversion would occur if the library source unit was ‘None’.
I then assume that this can be fixed with setting the new RDocument in InsertScriptItem.prototype.beginEvent its unit to ‘None’. Not knowing what the intended behavior should be for any other case, source or usage ...
Regards, CVH
|
|
2516 | QCAD Bugtracker | QCAD (main) | Bug Report | Low | Screen-based Linetypes issues with pixel based line wid ... | Closed | | CVH |
Task Description
Andrew,
Related topics: https://www.qcad.org/rsforum/viewtopic.php?f=33&t=10567 https://www.qcad.org/rsforum/viewtopic.php?f=32&t=10563
Regards, CVH
|
|
1747 | QCAD Bugtracker | QCAD (main) | Bug Report | Medium | Scaling w 2 ratios fails to scale polyline arc | Closed | | CVH |
Task Description
Scaling without keeping the aspect ratio fails to scale an arc to an ellips when this is part of a polyline.
Discovered while documenting feature request ‘Skewing’
CVH
|
|
2380 | QCAD Bugtracker | QCAD (main) | Bug Report | Low | SaveAs doesn't always open the associated path of the a ... | Closed | | CVH |
Task Description
QCAD Professional Win 7 WinInstaller
Version: 3.27.0.0 (3.27.0) Internet: QCAD.org Build Date: Nov 30 2021 Revision: 62c65de Qt Version: 5.13.2 Architecture: i386 Compiler: Unknown
Related topic: https://qcad.org/rsforum/viewtopic.php?f=31&p=37972#p37964
In script SaveAs.js on line 104 the sourced filename is correct. When this is not empty on line 147 the fileDialog should select this file in its own path. The testing sequence in the topic shows this is not always the case. I am using the system file dialog.
Firts setting the corresponding folder for the fileDialog seems to fix this: 147 if (fileName.length!==0) { 148 fileDialog.setDirectory(fileInfo.absolutePath()); 149 fileDialog.selectFile(fileInfo.absoluteFilePath()); 150 } 151 else { ....
Regards, CVH
|
|
1638 | QCAD Bugtracker | QCAD (main) | Bug Report | Low | SansNS.cxf coding mismatch | Closed | | CVH |
Task Description
Some 50 glyphs in SansNS.cxf start with [#.... instead of [.... These glyphs are replaced by a ? when used. Merely removing the # fixes this. Corrected file included.
|
|
2482 | QCAD Bugtracker | QCAD (main) | Bug Report | Low | RShape::getIntersectionPointsCC still failing for touch... | Assigned | 1 | CVH |
Task Description
Andrew,
Referring to this forum post: https://www.qcad.org/rsforum/viewtopic.php?f=74&t=10152
With radii 1341.35667735 and 26 the relative tolerance is 0.00683678 and exceeds the former used fixed tolerance of 1e-4.
These arcs will then be considered to be tangent and the intersection point is 0.31024 units to the left of where we expect it.
Implemented: https://github.com/qcad/qcad/commit/77ae3e4518cc34f178779d2d2c724adcf80c229d#diff-dcc4e31eaeaed5a047f65dbce4ddda4bcd4d604e9e1005ee8481ded273768449
Updated: https://github.com/qcad/qcad/commit/071b60acd1176e6301bf6b6fcf716684221a97e8#diff-dcc4e31eaeaed5a047f65dbce4ddda4bcd4d604e9e1005ee8481ded273768449
I had already expressed my reserves on the relative tolerance but that was already a better solution for small arcs: https://www.qcad.org/rsforum/viewtopic.php?f=33&t=8775&p=34907#p34907
We could limit the tolerance by: A- The smallest of the fixed and the relative. B- A relative tolerance based on R2 there circle 1 is forced to be the larger one.
This will never account for the position in the plane. At a certain point the tolerance will be less than the accuracy/certainty of the values.
Regards, CVH
|
|
2218 | QCAD Bugtracker | ECMAScript | Bug Report | Very Low | RPolyline.appendVertex() doesn't default to width = zer ... | Closed | 1 | CVH |
Task Description
When I use poly.appendVertex(vector, bulge) the polyline is finally created with NAN widths
This, while the signature explains that bulge, width1 and width2 default to zero. https://www.qcad.org/doc/qcad/latest/developer/class_r_polyline_entity.html#a9ee706e50d6cc267fc84a85b7c81d5e6
Regards, CVH
|
|
2495 | QCAD Bugtracker | ECMAScript | Bug Report | Very Low | RLine.isParallel(RLine) may return true for certain non... | Assigned | 1 | CVH |
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
|
|
2540 | QCAD Bugtracker | QCAD (main) | Feature Request | Low | Retain original handle when Hatch properties are change... | Assigned | 1 | CVH |
Task Description
Andrew,
When we alter about any property of a Hatch entity it seems to be recreated with a newer/higher handle. This doesn’t influence the drawing order in direct. But already changing the drawing order of a Hatch it is recreated as a new entity.
It starts to matters in drawing order when there are multiple entities with the same drawing order and that after save/reload. Entities with the same drawing order then receive a new drawing order based on the original but sequentially increasing based on handle.
Because a Hatch is recreated with a newer/higher handle each time a property changes it will thus always end up above the others with the same order even when the original was created earlier.
This is more pronounced when copying/pasting entities from a source to a target drawing. The original Hatch drawing order is retained but it will always be above existent entities with the same drawing order in the target drawing after save/reload.
Most other entities are probably just updated in situ. It is unsure to me at this point if merely updating a Hatch is even possible. And perhaps this is related to the addObject ForceNew flag what is false by default.
Regards, CVH
|
|
2370 | QCAD Bugtracker | QCAD (main) | Feature Request | Low | Retain global width / segment widths when reversing pol... | Assigned | 1 | CVH |
Task Description
Andrew,
Changing orientation of a polyline with RV or by changing it in the Property Editor clears the global width value.
Single line pieces as polyline default to CCW. Still the global width is cleared when trying to set them CW.
I didn’t update since 3.27.0 but reading this topic I suppose it still is valid. Related: https://www.qcad.org/rsforum/viewtopic.php?f=89&t=9362
Regards, CVH
|
|
2411 | QCAD Bugtracker | QCAD (main) | Feature Request | Low | Report hatching loop errors in the user defined coordin ... | Closed | 1 | CVH |
Task Description
Andrew,
In “Loop not closed at point 120.079/259.997.” we can not use the coordinate as such. With my preferences I would need 120,079;259,997 as a valid coordinate to enter in the command line. I do this ‘translation’ in between in Notepad.
Not that personally my boundaries are frequently off
Reported by <OttoZ> in: https://www.qcad.org/rsforum/viewtopic.php?f=89&p=38836#p38829 ‘Die Koordinaten lassen sich nicht kopieren, sonst könnte man zur Fehlstelle springen.’
In all cases the “/” is not a valid Cartesian coordinate separator. The dot at the end of the sentence is also not so common in QCAD.
Regards, CVH
|
|
2335 | QCAD Bugtracker | QCAD (main) | Bug Report | Low | Rendering solid hatches in scaled blocks | Closed | | CVH |
Task Description
Andrew, presumed not to be OS/version depending.
Referring to topic: https://qcad.org/rsforum/viewtopic.php?f=33&t=9073. An issue that has similarities with several topics, and some bug reports (closed or still open).
Solid hatches in blocks that are scaled up seems to be crippled. Very pronounced with arcs in the boundary. I suspect that the arc interpolation isn’t scaled along with the Block Reference scale.
Another issue exists for patterned hatches in blocks. I suspect that the hatch origin is kept as defined in the block.
Applying the block reference insertion point and at scale as an offset to the hatch origin while rendering would: - hatch the inserted block exactly the same as it is created in the block. - reduce lagging and increase pattern accuracy/coherency there the hatch origin is at the same distance to the hatch as it is in the block. I know this doesn’t solves anything when the block is created from entities and the hatch origin wasn’t close to the hatch itself.
Regards, CVH
|
|
2564 | QCAD Bugtracker | ECMAScript | Bug Report | Low | REllipse::getVectorTo(p) returns a vector to a major po... | Assigned | | CVH |
Task Description
Andrew,
If a given point p is on the major axis then REllipse::getVectorTo(p) returns one of the major points. In the code this is handled as a special case when the point is in-line (collinear) with the major axis. This is only correct for points p outside the ellipse. Or better: For points p outside the area between the focal points.
The correct solutions are: - if p equals the center ⇒ two vectors to the two minor points. - if p equals one of the major points ⇒ the major point itself. - if p is in between the focal points ⇒ two vectors mirrored over the major axis. - if p is on the unlimited axis but outside the focal points ⇒ the nearest major point.
The problem is now what to return on a duality with full ellipses. Or for an ellipse arc where two results are valid.
For example: RCircle::getVectorTo(p) returns an invalid vector when the point is near the center. Then there are an unlimited number of solutions.
Further discovered that the point related to the returned vector may fail x²/a²+y²/b²=1 Although almost on the ellipse within 2.299e-10 ... f(x,y) may return 9.5310 This example would fail REllipse::contains while the border is considered as inside.
Meanwhile implemented a ‘simple method’ to find the nearest point(s) on an ellipse. Fast converging in 3 steps, no trigs and very accurate, about 24 lines of code. f(x,y) returns mostly 1.000 with so far: - a minimum of 0.9999999999999997 - a maximum of 1.0000000000000007. In other words, it is only off for the last meaningful decimal digit.
With this all methods that are based on REllipse::getVectorTo(p) can be implemented very reliable with tolerance, border flag, ... and so on. By default the normal for a point is given with high accuracy and a tangent is that rotated. ... .. .
Regards, CVH
|
|
2165 | QCAD Bugtracker | QCAD (main) | Bug Report | Low | Rectangle with Size (RS) doesn't remember Fill, RoundCo ... | Closed | 1 | CVH |
Task Description
QCAD Professional Win installer 32bit Version: 3.25.2.7 (3.25.2.7) Internet: QCAD.org Build Date: Dec 16 2020 Revision: e06f230 Qt Version: 5.13.2 Architecture: i386 Compiler: Unknown
Topic: https://qcad.org/rsforum/viewtopic.php?f=33&t=7900 Report: https://qcad.org/rsforum/viewtopic.php?f=33&t=7900#p30977
Rectangle with Size (RS) doesn’t update the Fill, RoundCorners & Radius settings shared under the [Shape] header in QCAD ini.
Explained as group synchronization while the Polygon methods have more settings in common, although not shared.
In the summary there are more minor issues listed. All have a bar in the Options Toolbar that disappears after the first is drawn.
I rather would opt for all individual settings ... ... or all grouped.
Regards, CVH
|
|
2517 | QCAD Bugtracker | QCAD (main) | Bug Report | Low | QCAD cursors being malformed. | Closed | 1 | CVH |
Task Description
Andrew,
Related topic: https://www.qcad.org/rsforum/viewtopic.php?f=8&t=10562
From the looks of it the cursor image data is read at a wider pace as it is stored. One can distinguish the double cross positioning QCAD cursor but it is shifted.
Regards, CVH
|
|
1756 | QCAD Bugtracker | QCAD (main) | Bug Report | Low | Polyline area wrong if polyline contains arc segments | Closed | | CVH |
Task Description
The area of polylines with arcs can be incorrect. With only line segments it is correct as far as I can check. See <Poly-line Area.dxf> ; <Poly-arc Area.dxf>
It does not depend on the quadrant their in nor with what point the start point is. It is related with the oriëntation. Flipping or mirroring horizontally induce the error.
Modifications like flip, move & copy may induce another error that locks the oriëntation. It is noticed that the oriëntation property in the editor does not change anymore when reversing. Although locked the value of the area property switches between good and wrong.
The master poly in question is a part of an arc and a part of an ellipse exploded 1024/full. These where recombined to one poly with ‘Create from selection’ and are closed. Closed as per the last vertex does not point to the start point, logically closed I presume. The purpose is to sum the error surface for the skewing math. For now I will use my common sence to distinguish what value is the correct one. Reversing while found faulty is the solution.
Version: 3.20.1.0 (3.20.1) Internet: QCAD.org Build Date: Apr 13 2018 Revision: dd51609 Qt Version: 5.5.1 Architecture: i386 Compiler: MSVC++ 10.0 (2010) Win7 32bit
Regards
|
|
2302 | QCAD Bugtracker | QCAD (main) | Bug Report | Very Low | polygon.getSelfIntersectionPoints(tol) returns 3th inva... | Assigned | 1 | CVH |
Task Description
Windows 7 pro 32 bit msi-Installer Version: 3.26.4.5 (3.26.4.5) Internet: QCAD.org Build Date: Jul 20 2021 Revision: e596276 Qt Version: 5.13.2 Architecture: i386 Compiler: Unknown
Andrew,
In the attached dxf: Besides that it is clear that duplicate vectors are not filtered ... Where a segment is crossing in another node a non valid node is returned as self-intersection point. Seems to be unrelated to CW/CCW or tolerance.
Where 2 nodes coexists 4 duplicate vectors are returned.
Regards, CVH
|
|
1925 | QCAD Bugtracker | QCAD (main) | Suggestion | Low | Poly Ref Points manipulation that generates null-segmen ... | Closed | | CVH |
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
|
|
2126 | QCAD Bugtracker | QCAD (main) | Suggestion | Very Low | PE casts on individual hatch segments | Closed | 1 | CVH |
Task Description
QCADpro 3.25.2.1 / win7pro 32 bit / 4GB / 1e generation i7 2.6Ghz / HDD GeForce GT 520
The method PE casts the clipboard on individual hatch segments. Hatches should be considered as a single complex entity not allowing certain actions.
Discovered while: https://qcad.org/rsforum/viewtopic.php?f=33&p=30008#p30008
Not that it matters: In doing so the scaling is off too.
Regards, CVH
|
|
1928 | QCAD Bugtracker | QCAD (main) | Feature Request | Low | Optionnally 'Auto clean up' after generation of NaN / N... | Assigned | 1 | CVH |
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.
|
|
2016 | QCAD Bugtracker | QCAD (main) | Bug Report | Low | Offsetting multi selection of polylines halts premature | Assigned | 1 | CVH |
Task Description
See: https://qcad.org/rsforum/viewtopic.php?&t=6827&p=25992#p25992
Offsetting 32 polys from ellipses fails. Offsetting 16 polys can be completed with 2 selections for outer and 2 for inner.
For some reason the offset function halts premature.
Regards, CVH
|
|
2558 | QCAD Bugtracker | QCAD/CAM | Bug Report | Low | Offset trajectory path issue with circular Lead In/Out | Waiting on User | | CVH |
Task Description
Andrew,
Please refer to related forum topic: https://www.qcad.org/rsforum/viewtopic.php?f=74&t=10724#p44206
An eighth circle with radius 8 Lead In/Out relates to nothing in the actual exported cutter trajectory. Nor does it with the edge being cut.
Proper examples and a comparison with ‘Extension’ type Lead In/Out included. Conclusion: IMHO connecting the cutter trajectory and edge being cut is wrong.
It looks a lot like turning on Cutter Compensation (G41/42) while the motion is circular. But that is uncommon because most controllers can not cope with this motion. One can increase the offset gradually along a straight pre-entry segment for turning on G41/42 but not along a circular path. Also see snippet: - Pre-entry C→B turning on G41 - Circular Lead In B→A
Regards, CVH
|
|
2311 | QCAD Bugtracker | ECMAScript | Bug Report | Low | Odd self-intersection point for spline shapes | Closed | | CVH |
Task Description
Andrew,
Encountered with snapshot 3.26.4.9 On both a 32bit win7 and a Linux machine. But probably not related to version nor OS.
The calculated area centroid position for a self-intersecting shape is invalid. Therefor polylines and splines are checked for their self intersection nature. Polylines with line segments require a tolerance of 1e-6. For polylines with arc segments there is no easy to formulate value. Reverted to something less strict than the arc connect tolerance: 1.1e-3 Refer to: https://www.qcad.org/rsforum/viewtopic.php?f=30&t=8526&p=34056#p33694
RSpline.getSelfIntersectionPoints() has no tolerance value.
Some perfect valid spline shapes fail this test. Not related to the XP spline approx tolerance preference. Related to orientation, try the failing shape when reversed in situ. Related to their position in the plane, see translated examples.
Reproducible with control point splines. Reproducible when rotating the shape. Such failing closed splines can be hatched and an area centroid is returned.
Regards, CVH
PS: Got a notice posting this: “Notice: Trying to access array offset on value of type bool in /home/qcadch/public_html/bugtracker/scripts/details.php on line 222”
|
|
1752 | QCAD Bugtracker | QCAD (main) | Bug Report | Low | Not selecting text with sub/superscript | Closed | | CVH |
Task Description
Found a strange behaviour with formatted text.
File attached. ‘Draw’-selecting only the yellow text with a little space arround it - L>R or R>L ⇒ Yellow text not selected.
‘Draw’-selecting only the yellow text with a little space from R>L but crossing the text half way - Yellow text Selected ⇒ Expected behaviour.
‘Draw’-selecting just including the mentioned little circles. - Orange L>R or R>L ⇒ Normal texts selected ⇒ Expected behaviour - Green L>R Yellow not R>L Yellow selected ⇒ Expected behaviour - Magenta L>R or R>L ⇒ Yellow text not selected ?? - Red L>R or R>L ⇒ Yellow text not selected ??
Version: 3.20.1.0 (3.20.1) Internet: QCAD.org Build Date: Apr 13 2018 Revision: dd51609 Qt Version: 5.5.1 Architecture: i386 Compiler: MSVC++ 10.0 (2010) Windows 7 32-bit
Kind Regards
|
|
2488 | QCAD Bugtracker | QCAD (main) | Feature Request | Low | Not saved/loaded custom properties when the title is no ... | Closed | 1 | CVH |
Task Description
Andrew,
Discovered in writing a custom tool: hatchEntity.setCustomProperty(”MijnEPB”, “Ruimte”, roomData.numberText); Works perfectly and I can retrieve the room numbers of all semi-automatically placed hatches in this instance of QCAD.
But I can not store and reload this file with these custom properties to use them in a new QCAD session. I then assume the title must be ‘QCAD’. Then I wonder how QCAD handles custom properties by other CAD applications. Are they also removed on loading/writing?
QCAD doesn’t list these custom properties in the Property Editor. Here hidden was fine unless they are not stored with the document.
Is it even possible to store them in the drawing file? Why is the title a required variable when it can’t differ from ‘QCAD’? Would it be possible to list them up in the Property Editor because I know they are filtered on title ‘QCAD’.
For now I revert to: hatchEntity.setCustomProperty(”QCAD”, “EPB-Ruimte”, roomData.numberText); Similar as the CAM tool that uses ‘Cam....’ for all keys.
Regards, CVH
|
|
2194 | QCAD Bugtracker | QCAD (main) | Bug Report | Very Low | Multiple selection of entities with custom properties d ... | Closed | 1 | CVH |
Task Description
QCAD Professional Win7 installer 32 bit Version: 3.25.2.13 (3.25.2.13) Internet: QCAD.org Build Date: Feb 12 2021 Revision: cad2d36 Qt Version: 5.13.2 Architecture: i386 Compiler: Unknown
In the file provided one would expect *VARIES* in the property editor under custom properties when selecting 2 or more entities. The key list is reduced to what keys are common to the multiple selection. (Here 3) The values displayed are inconsistent depending the selection.
Select All » 3 custom properties of line 3 Select the 3 vertical » 3 custom properties of line 2 Select the first vertical and the diagonal » 3 custom properties of line 1 Select all but the first vertical » 3 custom properties of line 3 And so on ...
Regards, CVH
|