This is more than a branded splash though as it lets you quickly customise the Inkscape experience to suit what you need to work on. Well, the first time you open Inkscape 1.1 you are greeted by a new welcome screen. GIMP, Photoshop, et al are raster graphics editors which works with pixels at a fixed resolution. Rather like LibreOffice, Firefox, and Blender, Inkscape is regularly cited as an example of how powerful and capable open source software can be.Īnd today’s Inkscape 1.1 underlines that fact superbly.īut in case you’re new to it: Inkscape is a vector graphics editor used for editing vectors (resolution-independent shapes that scale perfectly). Inkscape is regularly cited as an example of how powerful open source software can beĬhances are you’re already familiar with Inkscape, or have at least heard of it before. This update to the open-source vector graphics editor comes with a number of new features and workflow enhancements, ranging from a new handy new welcome screen to new formats to export finished work to. Looks like I can’t put 2 dropbox links into this message so I will follow with another message with a link to the svg test file.Good news for open source creatives as Inkscape 1.1 has been released! Otherwise all I can use this for is just engraving art or other things where scale is not important.Ĭan you please start by ensuring that the scale on the rulers in the user interface accurately reflects the size that will be cut? I’m looking into other options to make this cutter usable, like perhaps grbl or benbox “if” I can get those to work with this machine, or just replacing the controller with something that works with MACH3. Then I’ll worry about getting the dxf and svg files to load correctly with proper scale. One step at a time… please fix whatever is causing the laser to cut at a different scale than what is shown on the rulers in the UI. The scale in the UI does not even make sense. Nevermind for now the fact that the files won’t load with the correct scale (each of those squares is supposed to be 15mm wide). The svg file should be smaller than 30mm but it is much larger. You can clearly see that according to the scale marks in the UI, the 3 boxes in the svg file should be smaller than the scale test (look at where the arrow points to 30mm on the scale). ![]() Putting that aside for the moment, this test case should be easy to reproduce using mlaser 2.4. I cannot seem to load a dxf or svg file with correct scale. I have placed arrows pointing out the 30mm spot on the mlaser UI in both instances. Note that both images of the mlaser UI show a mm scale at the top. I loaded the 30mm test file, ran the laser, then loaded the svg file and ran the laser without moving the paper or making any other changes. You can see the 30mm scale bitmap test file loaded in mlaser 2.4, an svg file loaded in mlaser, and the resulting cuts. Using mlaser for any work that needs accurate scaling seems nearly impossible without a bunch of work to try to compensate for this. Check if QMAKE_INFO_PLIST points to a valid file.Ĭould you please check this file into the repo? ![]() Project WARNING: Fervor: falling back to application name 'mLaser' Trying to build on my Mac, I am stuck at: simac:MLaser simon$ /opt/local/libexec/qt5/bin/qmake src/MLaser.pro QMetaObject::connectSlotsByName: No matching signal for on_btnItly_clicked() QMetaObject::connectSlotsByName: No matching signal for on_comboBoxSerial_activated(QString) QMetaObject::connectSlotsByName: No matching signal for on_btnOK2_clicked() QMetaObject::connectSlotsByName: No matching signal for on_btnOK1_clicked() QMetaObject::connectSlotsByName: No matching signal for on_toggleLaser_valueChanged(int) ![]() QMetaObject::connectSlotsByName: No matching signal for on_btnNext_clicked() "Bluetooth-Incoming-Port" "incoming port - Bluetooth-Incoming-Port" "" 10:32:04.444 mLaser There was an error parsing the ist for the bundle at URL : NSCocoaErrorDomain - 3840 Started via terminal, I see the following first lines: simac:src simon$ /Applications/mLaser.app/Contents/MacOS/mLaser
0 Comments
Leave a Reply. |