![]() ![]() In the end I wouldn't even know how good CAD tools would have to look like in Inkscape, I wouldn't know what to propose or ask for, very concretely.Hot Door did not "take advantage of the situation" with the Adobe Illustrator upgrade. I think Inkscape is a great program and really a total open source success story - it really works very, very well. Or I would just provide values, which can be done in XML editor but not as easily as in CAD software). (Whereas in CAD I would grab a reference point instead of the object itself, this can't be done in Inkscape (I think). Instead of, like in CAD, immediately provide all parameters and see it appear in place.įor instance, if you need to move object A to a certain distance from object B: first place it on top of object B, then move it (with mouse, arrows, by editing XML or by using transformation dialog). Only the approach is different.Ĭoming from CAD, I think the biggest change in way of thinking is: first duplicate or create an object in place, then transform. ![]() Using the XML editor, the transformations dialog (Ctrl+Shift+M, allows relative and absolute values), guides and double-clicking on them (allows absolute and relative moves, so by duplicating a guide and then relative-moving it, you can create offsets), align and distribute with its many options (Ctrl+Shift+A), object/grid snapping, etc, almost anything can be done. In the end however I think best thing to do is a shift of mindset, leave CAD and become an Inkscaper (when in front of Inkscape), learn to achieve the same results with native Inkscape features. It's not exactly crucial to have this in Inkscape, but having gotten used to CAD-like ways of controlling translations, scaling, rotations etc, I sometimes miss them (especially when doing geometrical/symmetrical/technical like drawings). I was interested in this too, having worked a few years with AutoCAD. Anyway, still stepping a little in the dark. For the time being I have dowloaded the release you told me and I'm testing something here and there. In this case, if those files have not been deleted, it should be enough to uncomment the line shown by suv. If the only step required (apart from merge) is to uncomment a line of a file, I don't see many problems in doing it.Īs you are using those tools, could you list me the ones working and the ones leading to crash? If I will be able to do it, I'd like to release a version with no easter eggs insideĮDIT: I guess that Uwe Scholer does not own any branch, so everything should be already in the trunk. I'm waiting for the further development of the BSpline tool and then I will try to merge those two branches in one with LPE enabled. I will have to investigate a bit, but I guess it is possible. What would be super generous of you would be to compile it to have the Livespiro, Bspline AND these experimental LPEs all in the same build. I use the Uwe build myself, but let me know if you compile and make a windows build available. On that same thread there's a link to a video that's also very nice. I don't know if that's enough info for you to compile it yourself. You can try out the draft version of these path effects but do note that some of them don't work at all and will immediately crash your Inkscape.Ĭompiling this version for yourself is a little more complicated but there are instructions -from ~suv, when ~suv used to post on this forum here. Druban wrote:Hi Brainless, I can point you to the page with the last development version(r11789) that Uwe Scholer compiled containing these experimental LPEs for Windows.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |