Isn't that right?
A 24" by 8" window would automatically convert to 609.6mm by 203.2mm in a millimeter unit drawing.
The same would happen if you import a dxf in inch into a drawing in mm ...
Regards,
CVH
Moderator: andrew
No, not even close ...
Why is it automatically converting the unit? There is no need to convert anything! I've used plain numbers for the window without a unit what means that it has to use the global unit set below Drawing Preferences. 24 by 8 would then be 24 mm by 8 mm and not 609.6mm by 203.2mm,
No, that isn't the same! That is a completely different story because I did not import or Copy/Paste from one unit drawing to a different unit drawing. My drawing is set to mm and there is no need referring to the task to convert anything.
Installed it on a 64-bit computer there the 32-bit installer won't run.
I am comparing it with the library Browser ...
I think that this is confirmed ... ScriptItems are firts created on a new offline document.
That is concerning.. it sounds like a Windows Installer issue... I may of messed up in my steps in deployment doing both 64 and 32 bits.Some short remarks picked up on the Win10 64bit PC ... All in a hurry
(32bit msi fails to run )
I've set the duct fitting angles as fixed to align with SMACNA's angles. So when doing duct loss calculations you are going by what's available. What I want to do in the future is have a utility to export ductwork to an external app to run calculations (equal friction, equivalent length, static regain) so the duct fittings must align to SMACNA. The only issue I have is running vertical ductwork atm.. but I have an idea- I would prefer a combobox for an elbow with an arbitrary angle.
I also like the RMathLineEdit functionality throughout QCAD.
I agree, I need to change so that the width is grayed out when selecting and perhaps a custom property as you said.- I understand that appendages can be added aligned at any line or line segments.
The size is then related to the selected line/segment and not to the options what is not grayed out.
On a duct 100mm by 2m (a polyline) that may also propose a 2m wide elbow.
Could the appendages tools made so that the length of a duct is omitted as candidate ...
... Thinking of adding a custom property 'Width' ...
I does absolutely nothing! I use a common core for all the structural scripts so I'll have to bypass the getAuxPreview in this case.- Structural Pipe: What does endpoint do?
Darn.. missed that. It's suppose to copy the AIA.db from the ../QCAD/utility/data folder to your RSettings.getDataLocation (so that it can be edited by the user). It currently uses the basePath to determine the location of the original and then copy it to the RSettings.getDataLocation()... I need to change it from the basePath to the QCoreApplication.applicationDirPath.- "The Layer Manager tools database has most common combinations of layers ... "
My dropdowns are empty and do not accept editing.
>aia.db< Seems to hold relevant textual readable data.
No copy of >aia.db< under C:\Users\
Must I copy that over myself?
For the life of me I don't know where I got the term Block Script.... I'll change that to Browser Script I think.What I find misleading is that the help file states "The Window utility is a block script to a draw bi-fold door ..."
First, it's not drawn as a block and second, it's not a door either ...
I do understand that ... Your tools can be used to draw piping too.
I think that it is no good idea to change the App.Prefs. unless you correct it back ... See DrawFromCSV beginEvent.
Code: Select all
unit = RSettings.getIntValue("UnitSettings/Unit", RS.Millimeter);
Mike,
In my case it existed ... On both computers.
Code: Select all
var destDir = new QDir(destDirPath);
if (!destDir.exists()) {
destDir.mkdir(destDirPath);
}
Code: Select all
downloadToFile(QUrl.fromLocalFile(sourceName).toString(), RSettings.getDataLocation(), "AIA.db", 10000);