|
1793 | QCAD (main) | Bug Report | Low | Ruler functionality is compromised by Auto Grid setting | Closed | |
1 |
Task Description
Regarding to an observation by the forum member Horst1803 http://www.qcad.org/rsforum/viewtopic.php?f=92&t=5725
The ruler functionality is compromised by Graphics View / Grid settings. To show the full Ruler functionality “Automatic scale grid” has to be activated. I think that is not intended behavior.
Case: Appearance / Show rulers = activated
Application Preferences / Graphics View / Grid
on - Automatically scale grid on - Automatically scale meta grid off - Solid grid lines = Rulers visible = Graduation visible = Labels visible
off - Automatically scale grid on - Automatically scale meta grid off - Solid grid lines = Rulers visible = Graduation invisible = Labels invisible
|
|
1519 | QCAD (main) | Bug Report | Low | Ruler precision always zero | Closed | |
|
Task Description
Rulers show only whole numbers.
|
|
1087 | QCAD (main) | Bug Report | Low | Ruler ticks are not corresponding to the grid points | Assigned | |
|
Task Description
Ruler ticks are not corresponding to the grid points, Ruler will completely disappear at a certain zoom level,
Settings: Drawing unit: inch, Grid settings: Grid 1, Meta Grid 12, Dim Label Format: “Engineering, 0’-0.0”
see topic below: http://www.qcad.org/rsforum/viewtopic.php?f=32&t=3014
|
|
103 | ECMAScript | Feature Request | Low | Runtime reload script | Closed | |
|
Task Description
As of TP1, a script once loaded into the runtime, does reflect changes to the file it was loaded from only after a restart of the whole of QCAD. This adds a considerable time overhead to developing scripts. Therefore I want to suggest a reload mechanism, that works kind of like the one known from a web browser.
As there is no clear separation between users custom scripts and ribbonsoft supplied scripts, checking the modification time for every access to any script might prove a performance hit.
Possibly a user script can be written, to invalidate another certain script and have the runtime reload it from file? I could add that to my menu.
Or as some magic, that can be written to “MyAction.init()”?
|
|
545 | QCAD (main) | Bug Report | Low | russian codepage error in Layer list | Closed | |
|
Task Description
1. Creating new file 2. create new layer with cyrilic name, ex.: фыва screenshot #1 3. saving 4. closing 5. look in file see correct UTF-8 name screenshot #2 6. opening file via qcad/ oops! layer name is incorrect screenshot #3 7. saving file 8. closing 9. look in file. got incorrect version
my guess, that the problem is that whole file is encoded as ANSI:
$DWGCODEPAGE
3
ASCII
9
but layer names are coded as UTF-8. so additional converting ANSI→UTF-8 is demanded
|
|
548 | QCAD (main) | Bug Report | Low | russian codepage error in text tool | Closed | |
|
Task Description
1. add any russian (cyrillic, for example йцук) text via text tool 2. save file 3. close file 4. open file 5. voila (see attached screenshot)
|
|
1 | QCAD (main) | Bug Report | Very Low | Sample Task | Closed | |
|
Task Description
This isn’t a real task. You should close it and start opening some real tasks.
|
|
1638 | QCAD (main) | Bug Report | Low | SansNS.cxf coding mismatch | Closed | |
|
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.
|
|
38 | QCAD (main) | Feature Request | Very Low | Save / restore, export / import settings | Closed | |
|
Task Description
Inside the application preference dialog:
save settings (asks for a name)
restore settings (picked from a list that contains all so far saved settings and some presets)
export settings (to a file)
import settings (from a file)
Export / import could be useful for companies to synchronize settings.
|
|
783 | QCAD (main) | Feature Request | Low | Save as .dgn option missing in 3.0.8? | Assigned | |
|
Task Description
Not really a bug I suppose but the save as.dgn file format is missing in snapshot 3.0.8 release.
Will this be available again soon?
|
|
65 | QCAD (main) | Bug Report | Low | Save as hotkey | Closed | |
|
Task Description
File - Save As has no hotkey under Linux (should be Ctrl-Shift-S)
|
|
474 | QCAD (main) | Bug Report | Low | Save as of loaded file should save to same folder | Closed | |
|
Task Description
‘Save as’ of loaded file should save to same folder as loaded file.
|
|
71 | QCAD (main) | Bug Report | High | Save fails with uncaught exception | Closed | |
|
Task Description
New File
Save, enter name without extension
Uncaught exception at /home/martin/workspace/rsframework/scripts/File/SaveAs/../Save/Save.js:40: TypeError: Result of expression 'di.getCorrectedFileName' [undefined] is not a function.
40 fileName = di.getCorrectedFileName(fileName, fileVersion);
|
|
203 | QCAD (main) | Bug Report | Low | Save font styles bold and italic | Closed | |
|
Task Description
Font styles “bold” and “italic” are not saved to file.
According to http://docs.autodesk.com/ACD/2011/DEU/filesDXF/WS1a9193826455f5ff18cb41610ec0a2e719-7a4d.htm it is saved in dxf as group code 1071 and according to http://www.autodesk.com/techpubs/autocad/dxf/dxf2002.pdf page 20 its type is “Extended data 32-bit signed long”.
|
|
44 | QCAD (main) | Bug Report | High | Save might not save in last chosen format | Closed | |
|
Task Description
File - Save might not save in last chosen format but default format. E.g. if a file is saved as DXF R12, and then saved, check if the format is still DXF R12 and not the default DXF format (2010).
|
|
153 | QCAD (main) | Bug Report | Low | Save triangle shape after exploding dimension | Closed | |
|
Task Description
Save triangle shape after exploding dimension
|
|
700 | QCAD (main) | Bug Report | Low | Saved 'hatched' block loses hatching when using isometr... | Assigned | |
|
Task Description
Hatched block loses hatching when using isometric projection tool: See -http://www.qcad.org/rsforum/viewtopic.php?f=32&p=7063#p7063
When manipulating a saved hatched block with the isometric tool it loses the hatching unless the block is exploded.
Is this normal behaviour here? or a bug?
|
|
911 | QCAD (main) | Bug Report | Low | Saving / loading text with accents ('é') | Closed | |
|
Task Description
Text with é turns into È.
|
|
1732 | dxflib | Bug Report | Low | Saving dimension with custom text position | Closed | |
|
Task Description
Custom text position must be written as type flag (code 70, flag 128) as well as in style overrides as codes
1070
279
1070
2
|
|
1903 | QCAD (main) | Feature Request | Low | Saving layer settings, e.g. visibility status, associat... | Assigned | |
|
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.
|
|
1246 | dxflib | Bug Report | Low | Saving MText with linefeeds in escaped text causes corr ... | Closed | |
|
Task Description
Saving MText with linefeeds in escaped text causes corruption of file.
See: http://www.qcad.org/rsforum/viewtopic.php?f=76&t=3593
|
|
46 | QCAD (main) | Bug Report | High | Saving solid filled hatch hits assert | Closed | |
|
Task Description
Debug: RDwgExporter::exportHatchEntity: RHatchEntity(REntity(RObject(id: 27, document: "0xbad0940", address: "0xffffffffaba45558", undone: 0), type: 20, layerId: 21, blockId: 22, lineweight: -1, linetypeId: 0, color: RColor(ByLayer) , drawOrder: 3 , selectionStatus: false ) , solid: true, scale: 2, angle: 0, pattern: "SOLID",
boundary:
loop 0:
RLine(RShape(address: "0xffffffffaba42b48"), startPoint: RVector(8, 25, 0) , endPoint: RVector(35, 25, 0) )
RLine(RShape(address: "0xffffffffaba42d88"), startPoint: RVector(35, 25, 0) , endPoint: RVector(35, 9, 0) )
RLine(RShape(address: "0xffffffffaba42c08"), startPoint: RVector(35, 9, 0) , endPoint: RVector(8, 9, 0) )
RLine(RShape(address: "0xffffffffaba43150"), startPoint: RVector(8, 9, 0) , endPoint: RVector(8, 25, 0) )
)
Debug: "RDwgServices::printErrorStackTrace: Not applicable"
Warning: RDwgExporter::exportEntity: Exception occured. Entity NOT saved:
RHatchEntity(REntity(RObject(id: 27, document: "0xbad0940", address: "0xffffffffaba45558", undone: 0), type: 20, layerId: 21, blockId: 22, lineweight: -1, linetypeId: 0, color: RColor(ByLayer) , drawOrder: 3 , selectionStatus: false ) , solid: true, scale: 2, angle: 0, pattern: "SOLID",
boundary:
loop 0:
RLine(RShape(address: "0xffffffffaba42b48"), startPoint: RVector(8, 25, 0) , endPoint: RVector(35, 25, 0) )
RLine(RShape(address: "0xffffffffaba42d88"), startPoint: RVector(35, 25, 0) , endPoint: RVector(35, 9, 0) )
RLine(RShape(address: "0xffffffffaba42c08"), startPoint: RVector(35, 9, 0) , endPoint: RVector(8, 9, 0) )
RLine(RShape(address: "0xffffffffaba43150"), startPoint: RVector(8, 9, 0) , endPoint: RVector(8, 25, 0) )
)
Fatal: ASSERT: "false" in file RDwgExporter.cpp, line 1234
Thread [1] 23860 (Suspended : Signal : SIGABRT:Aborted)
__kernel_vsyscall() at 0xffffe424
raise() at 0xb4f037ff
abort() at 0xb4f05140
RMainWindow::messageHandler() at RMainWindow.cpp:63 0x8e06a4a
qt_message_output() at 0xb5357f65
0xb53581ab
qFatal() at 0xb53582c9
qt_assert() at 0xb5358355
RDwgExporter::exportEntity() at RDwgExporter.cpp:1,234 0x8cbb4cf
RExporter::exportEntities() at RExporter.cpp:408 0x8de9f8e
<...more frames...>
|
|
40 | QCAD (main) | Bug Report | Medium | saving spline CP, 2deg, closed hits assert | Closed | |
|
Task Description
new file
draw spline CP, 2deg, closed
save → crash
Debug: "RDwgServices::printErrorStackTrace: General modeling failure"
Warning: RDwgExporter::exportEntity: Exception occured. Entity NOT saved:
RSplineEntity(REntity(RObject(id: 23, document: "0xb246720", address: "0xb915f00", undone: 0), type: 23, layerId: 21, blockId: 22, lineweight: -1, linetypeId: 0, color: RColor(ByLayer) , drawOrder: 0 , selectionStatus: false )
controlPoints (6): 0: RVector(14, 21, 0) 1: RVector(41, 25, 0) 2: RVector(41, 9, 0) 3: RVector(28, 4, 0) 4: RVector(14, 21, 0) 5: RVector(41, 25, 0)
fitPoints (0):
knots (7): 0: -1, 1: 0, 2: 1, 3: 2, 4: 3, 5: 4, 6: 5, )
Fatal: ASSERT: "false" in file RDwgExporter.cpp, line 1234
Thread [1] 2066 (Suspended : Signal : SIGABRT:Aborted)
__kernel_vsyscall() at 0xffffe424
raise() at 0xb4f037ff
abort() at 0xb4f05140
RMainWindow::messageHandler() at RMainWindow.cpp:63 0x8e025a6
qt_message_output() at 0xb5357f65
0xb53581ab
qFatal() at 0xb53582c9
qt_assert() at 0xb5358355
RDwgExporter::exportEntity() at RDwgExporter.cpp:1,234 0x8cb754f
RExporter::exportEntities() at RExporter.cpp:408 0x8de5c96
<...more frames...>
|
|
855 | QCAD (main) | Feature Request | Low | Scale dimension on/off option ... | Closed | |
|
Task Description
QCAD 3.1.5 - has a new “Dimensioning Scale adjustment option” (Property editor/Linear Factor). NICE!!!
What means - we are now able to change the dimension scale for existing dims!
My Feature request refers to new dimensions and I think it would be perfect to have a “Scale Factor - On/Off Option” for all Dim Tools.
That would bring us in the position to copy / scale a part of our drawing for a detail view and we could just use us usual the dimensioning tools (with a scale factor) for the dimensioning task ....
|
|
845 | QCAD (main) | Feature Request | Low | Scale factor for dimensions | Closed | |
|
Task Description
Introduce scale factor for linear dimension entities.
Original request was:
It would be nice to have the possibility to enter dimensions in the form of a formula and still show up as a ‘normal’ dimension. This would greatly help in creating details in a different scale (say, 5:1) than the rest of the drawing. Creating details is quite often necessisary for small objects (when lines are too close together to distinguish at 1:1) if the drawing must be legible to mere humans...
Now one must calculate and manually enter all dimensions for the detail after scaling (and re-calculate every time something gets modified), this is quite error prone. Exploding the dimensions before scaling is not a real option: the arrowheads and texts then get scaled, too, wich is undesirable. Scaling back, modifying and then repeating the process is also not quite on the mark: small errors creep in due to finite precision in the calculations made during the scaling.
|
|
1187 | QCAD (main) | Feature Request | Low | Scale possibility for Info tools ... | Assigned | |
2 |
Task Description
Now - after enjoying the great new “Scale” option for Dimensioning I like to ask for the same scale option for the “Info tools”. It would be really nice to have more flexibility (without a pocket-calculator) in reading and displaying the Info tool results.
|
|
789 | QCAD (main) | Feature Request | Low | Scale tool - mouse-pointer - inversely proportional sca... | Assigned | |
1 |
Task Description
3.0.8. Bug Report or Feature Request ..... I’m not sure!
If I use the mouse-pointer in the Scale tool I’m not able to do an inversely proportional scale. x - y locked or unlocked doesn’t matter in combine with the mouse pointer ...
|
|
92 | QCAD (main) | Bug Report | Low | Scaled printing and line-widths | Closed | |
|
Task Description
When printing with a scale, eg. 1:10, line-widths are scaled too. They should not. 1) they become very faint in the printout, 2) line-width in CAD carries extra information (Andrew told me:)
|
|
1688 | QCAD (main) | Bug Report | Low | Scaling (SZ) selection by Mouse only proportional possi ... | Closed | |
|
Task Description
Tested with checked / unchecked button for proportional scaling - but it doesn’t matter.
|
|
2171 | QCAD (main) | Bug Report | Low | Scaling a block reference should not scale line type pa ... | Closed | |
|
Task Description
See also: https://www.qcad.org/rsforum/viewtopic.php?f=33&t=7948
|
|
394 | QCAD (main) | Bug Report | Medium | Scaling a drawing | Closed | |
|
Task Description
By scaling a drawing (base drawing) the text is OK in height but not in position
|
|
1463 | QCAD (main) | Bug Report | Low | Scaling also scales locked layers | Closed | |
|
Task Description
Hi,
Upon selecting and scaling multiple objects, locked layers are also scaled.
Expected: Locked layers are unaffected by any modification commands
Workaround: Manually unselect objects before scaling
|
|
1865 | QCAD (main) | Bug Report | Low | Scaling polyline with width by negative factor removes ... | Closed | |
|
Task Description
Create polyline with global width (e.g. 10)
Scale polyline by factors X=-1, Y=1
Polyline loses width
|
|
1747 | QCAD (main) | Bug Report | Medium | Scaling w 2 ratios fails to scale polyline arc | Closed | |
|
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
|
|
956 | QCAD (main) | Bug Report | Low | Screen based linetypes: splines, texts, dimensions | Closed | |
|
Task Description
Screen based linetypes not working for splines, texts (CAD fonts) and dimension arrows.
|
|
1728 | QCAD (main) | Suggestion | Low | Script bindings for Qt 5.9.4 | Closed | |
|
Task Description
Please add script bindings for Qt 5.9.4, thank you.
|
|
443 | QCAD (main) | Bug Report | Low | Script exception when selecting a spline with fit point ... | Closed | |
|
Task Description
Script exception when selecting a spline with fit points and a spline with control points
|
|
408 | QCAD (main) | Feature Request | Low | Script Macro recorder | Closed | |
3 |
Task Description
Having practically no experience in scripting, a recorder that one could activate to memorize repetitive tasks (ie: inserting several layers with different attributes when starting a new drawing)would a useful tool to help get a start on scripting.
|
|
1493 | ECMAScript | Bug Report | Low | script processing failure using -exec | Closed | |
|
Task Description
I have just updated from 3.11.0 to 3.15.5. Often, I load a script with the command format ..../qcad -exec ..../dims.js Note that the script filename is dims.
* Everything is satisfactory with 3.11.0 and always has been.
* qcad-3.15.5 runs satisfactorily without an -exec switch
* qcad-3.15.5 -exec same-file-as-for-3.11.0 crashes per the attached screenshot. The screenshot has been generated by adding the -enable-script-debugger switch.
* It appears that the script dims.js runs completely, and the crash happens as the script handler terminates. The qcad window is complete with the contents defined in dims.js, also qcad is usable normally. This qcad disappears when the debugger is terminated.
* This problem is totally repeatable.
|
|
426 | QCAD (main) | Feature Request | Low | Scriptable entities | Closed | |
|
Task Description
Provide script functionality for entities:
Paint or decorate entity, for example based on custom properties assigned to the entity
Listen and react to events
|
|
1178 | ECMAScript | Bug Report | Low | scripting definition point and vertical DIMs | Closed | |
|
Task Description
A regression? In my script I draw stacked dims (depth d):
var c = RVector.getAverage(a, b); // Zentrum der Messung
var dim = new RDimRotatedData();
dim.setExtensionPoint1(a);
dim.setExtensionPoint2(b);
c.x = a.x + d * 50 + ( d > 0 ? 50 : -50 );
dim.setDefinitionPoint(c);
dim.setRotation(Math.PI / 2);
Curiosly, this would work in 3.7.5 but fail in 3.7.7: the DefinitionPoint would be ignored then, but only in vertical ones, not in horizontal ones!
More curiously still: The DIM gets drawn right as soon as I move the setRotation call before the setDefinitionPoint call!
PS: the debugger proved very helpful again :)
|
|
230 | QCAD (main) | Feature Request | Low | Scroll bars optional | Closed | |
|
Task Description
Provide option to hide scroll bars.
|
|
1633 | Themes | Bug Report | Low | Scrollbar in dark theme | Closed | |
|
Task Description
The scrollbar in the dark theme remains visible when there are many levels. For example, it blocks some operations such as unlocking or blocking individual levels after you have blocked all levels.
|
|
250 | QCAD (main) | Bug Report | Low | Scrolling in Property Editor changes List Box elements | Closed | |
|
Task Description
Bug or Performance Issue? I’m not sure but it regularly trips me up and is counter intuitive.
In the right hand window generally if you scroll in the pane the list of items moves up and down as expected. E.g. Layer List and Block List.
However in Property Editor there are drop down list boxes and scrolling in the Property Editor pane dangerously scrolls elements within any drop down list that the mouse pointer happens to alight upon. This can lead to inadvertently changing properties.
I propose that a drop down list should not scroll until the list is opened. Scrolling in the Property Editor pane should scroll the Property Editor contents.
|
|
393 | QCAD (main) | Feature Request | Low | Scrolling with arrow keys | Closed | |
|
Task Description
Scrolling with arrow keys
|
|
550 | QCAD (main) | Feature Request | Low | Search / replace for (selected) text entities | Closed | |
|
Task Description
See also: http://www.ribbonsoft.com/rsforum/viewtopic.php?f=32&t=1923
|
|
644 | QCAD (main) | Feature Request | Low | Search for text | Closed | |
|
Task Description
Search for a text, highlight or select (?) the result(s).
|
|
975 | QCAD (main) | Feature Request | Low | Search/Replace accomplished info ... | Closed | |
|
Task Description
It would be nice to get a status information after the use of the “Search/Replace” tool.
Something like: “5 matches found and replaced”, or no “matches found”.
It helps allot to get an Idea what happens in your drawing. Right now the tool window will just disappear and you have no idea about any success.
|
|
1137 | QCAD/CAM | Bug Report | High | segfault creating dashed spline (without addons) | Closed | |
|
Task Description
Hello,
This is my first real bug report so please advise how i could provide more useful information.
I am not certain if the severity is correct.
The bug: segfault when creating a spline with a dashed linetype or opening a file containing one.
The bug isn’t present with the dwg extension installed
Steps to reproduce: 1. create drawing 2. create spline 3. set linetype to dashed 4. crash
|
|
295 | QCAD (main) | Bug Report | Low | SEGFAULT in Plugin.prototype.initDoc() | Closed | |
|
Task Description
Plugin.js:
/**
* \internal Called once on startup.
*/// TODO crashes under OpenSUSE 11.4
Backtrace:
Thread [1] 31002 (Suspended : Signal : SIGSEGV:Segmentation fault)
strncmp() at 0xb505089a
__xmlParserInputBufferCreateFilename() at xmlIO.c:2,525 0x92c27b9
xmlParserInputBufferCreateFilename() at xmlIO.c:2,559 0x92c284a
xmlNewInputFromFile() at parserInternals.c:1,549 0x9285697
xmlDefaultExternalEntityLoader() at xmlIO.c:3,881 0x92c45fd
xmlLoadExternalEntity() at xmlIO.c:3,941 0x92c46f6
xsltDocDefaultLoaderFunc() at documents.c:85 0x922b0d9
xsltParseStylesheetFile() at xslt.c:6,726 0x9224da3
RXslt::parseStylesheet() at RXslt.cpp:14 0x9212ce7
REcmaXslt::parseStylesheet() at REcmaXslt.cpp:196 0x8dff0e4
0xb6bd813c
0xb6ac1f68
0xb6a9164c
0xac23d732
0xb6a44262
0xb6a445f7
0xb6bb0f92
QScriptEngine::evaluate() at 0xb6bba46f
RScriptHandlerEcma::eval() at RScriptHandlerEcma.cpp:775 0x87d1bf4
RScriptHandlerEcma::doScript() at RScriptHandlerEcma.cpp:771 0x87d1ad8
RScriptHandler::init() at RScriptHandler.cpp:31 0x8f9bf9e
main() at main.cpp:218 0x87cb5bf
/rsframework/src/xml/xml/libxml2/xmlIO.c:
#ifdef HAVE_ZLIB_H
if ((xmlInputCallbackTable[i].opencallback == xmlGzfileOpen) &&
(strcmp(URI, "-") != 0)) {
if (((z_stream *)context)->avail_in > 4) {
char *cptr, buff4[4];
cptr = (char *) ((z_stream *)context)->next_in;
if (gzread(context, buff4, 4) == 4) {
if (strncmp(buff4, cptr, 4) == 0)
===> ret->compressed = 0;
else
ret->compressed = 1;
gzrewind(context);
}
}
}
#endif
|