- Inkscape Users - Inkscape Mailman

Re: [Inkscape-user] [Inkscape-devel] Spin slider widget: Opinions needed!
by Tavmjong Bah 04 Dec '17

04 Dec '17

On Mon, 2017-12-04 at 14:43 +0100, Eduard Braun wrote: > Hi Tav, > > thanks for looking into this! > > One question to get on the same page: > > This is about sliders like "Blur" and "Opacity" (which are re- > used > in some other places, too), right? However the actual color > sliders in the Fill and Stroke dialog are not affected? Yes... > Some thoughts from my side: > > > The "top part" dragging is very useful, we should have that. > > The "bottom part" dragging never felt quite right for me and > was > actually very confusing when I first started using Inkscape, > so > personally I'd be fine with dropping that. OK. That should be easy to do. > Having text and the spinner inside the widget is nice as it > saves a lot of space and creates a clean UI control that is > immediately recognizable as such (in contrast to multiple > controls loosely packed into a box with each other). > > If it's implementable with reasonable effort it's probably > good > to keep it, especially for locations where there is not much > room for an additional label and spinner (e.g. in the toolbar > of > the various tools that use the widget). It's not too hard (already done in my toy implementation). > The previous bullet point is only true if it's done right - > thanks to gtk3's wasteful use of screen space I'd consider > most > spinners in the toolbar broken right now (the label is > usually > hidden behind an ellipsis; due to the two huge buttons which > are > now placed side-by-side the usable width decreases even more, > so > we either need a more economic solution or need to rethink > the > use of spin sliders in the toolbar fundamentally. One can narrow the +/- buttons via CSS ( ,up, .down { padding:0; } ). I'll probably check this in (actually I'll probably set it to 2px, default is 8px). > > One performance consideration that might be worth to > have in mind when doing the rewrite: > > For some reason the custom spinner widget has > a much worse redraw performance than other spinner > implementations (e.g. the ones in the color selector): > > If I change opacity of an object the widget > only updates a few times per second and is redrawn with a > delay (canvas reflects the current value properly though). > In > contrast if I change the fill opacity of the same object > this > spinner widget redraws without noticeable delay. > > (strike that part - it only seems to affect the gtk2 build > and I > assume you won't backport this to 0.92.x) No, I won't be touching 0.92.x with this. > > TLDR: I kind of like the spin sliders like they are now for > "Blur"/"Opacity" (and could do without the bottom part > sliding), > however they waste too much space to be useful in toolbars > right > now. > > > Best Regards, > > Eduard > > > > > Am 04.12.2017 um 13:42 schrieb Tavmjong > Bah: > > > > > Hi, > > > > I've been looking into replacing the Gimp Spin Slider widget (e.g > > Blur/Opacity in the Fill and Stroke dialog). The widget is licensed > > under GPLv3 and is the only reason Inkscape as a whole is licensed > > under GPLv3 rather GPLv2.. The board sometime ago agree that being > > a > > GPLv2 program was desirable (I don't remember the exact reasoning). > > > > A normal Gtk Spin Slider (aka Gtk::SpinButton) has an option to > > show > > the "progress" of slider, that is the percentage (defined in some > > arbitrary way) between a minimum and maximum value. This in Gtk 2 > > is > > shown as a solid blue bar with width proportional to the value that > > covers the widget from top to bottom. In Gtk 3 the solid blue bar > > is > > replaced by a thin blue bar at the bottom of the widget. > > > > As far as I can tell, the Gimp version of the slider makes three > > changes: > > > > 1. It allows for a label inside the widget. This is a nice space > > saving > > feature. The widget handles changing the label text from black to > > white > > as the progress bar moves across the label. > > > > 2. It allows for a non-uniform scale by adding a "gamma" factor. > > > > 3. It adds the ability to drag the progress bar to change the > > value. If > > one drags from the top (down arrow cursor) the change follows the > > cursor directly. If one drags along the bottom half (double headed > > cursor) the change is finer and relative to the current value. > > > > I've always found that dragging the progress bar to be a bit > > awkward. > > One problem is that one can not start the drag at the far right of > > the > > widget as that area is reserved for typing a value directly in. > > Also, > > the different functionality of starting the drag in the top of the > > widget vs. the bottom of the widget is confusing. > > > > Since I am rewriting this widget, I can adjust it to what people > > want: > > > > * Do you want the progress bar? > > > > * If so, should it be the full height of the widget (quite a bit > > more > > complicated)? > > > > * Do you want to be able to drag the bar? With one/two methods? > > > > * Any other changes? > > > > Thanks, > > > > Tav > > > > > > > > > > > > > > > > > > ----------------------------------------------------------------- > > ------------- > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > _______________________________________________ > > Inkscape-devel mailing list > > Inkscape-devel(a)lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/inkscape-devel > > > > > > > > >

1 0

volunteer moderators needed
by brynn 28 Nov '17

28 Nov '17

Hi Friends, If anyone is interested, we still need more moderators for the website gallery. It doesn't usually take very much time. I'd estimate no more than a half an hour per week. (Preferably spread out 5 or 10 minutes each for 3 or 4 days per week. But at this point, once a week would help.) And Martin has built us a wonderful system where the burden of deleting an image or removing member doesn't fall all on one person. Typically it takes 2 moderators to decide the fate of a reported image or member. If interested, please visit this page, (https://inkscape.org/en/*moderators) and click the button which I think says something like "Join this team." After that, I'll contact you with details to get you started. All best, brynn

1 0

powerstroke on closed path bug?
by brynn 14 Nov '17

14 Nov '17

Hi Friends, I've seen a few times where applying Powerstroke LPE to a closed path not only doesn't work, but creates some strange results. This includes using the Triangle In/Out for Pencil and Pen, as well as applying it separately to a path. I thought it surely must be already reported as a bug, but I can't seem to find any reports. It could have a title with some technical words that I don't understand. I just want to make sure it's not going to be a duplicate if I report it. Is anyone aware of this being reported as a bug before, or knows which bug report it is? Or is this just such a known issue, that we don't expect it should work? Here's a test file: https://inkscapecommunity.com/jd/imgs/psclosed.svg Just add a powerstroke to that closed path. (Windows 7, 64-bit, Inkscape 0.92.2, 64-bit, 7z). Thanks, brynn

1 0

Inkscape.SNAP Snappy package do not export dxf files
by Luis Vasquez 08 Nov '17

08 Nov '17

Hi, i installed inkscape snap package and i can not export files to dxf. Some plugins are not installed numpy Failed to import the numpy or numpy.linalg modules. These modules are required by this extension. Please install them and try again.

2 2

Meeting - Inkscape Vectors
by Ryan Gorley 03 Nov '17

03 Nov '17

The Inkscape Vectors will be meeting a couple hours before the board meeting. Catch the agenda, time and location details here: https://gitlab.com/inkscape/inkscape-vectors/general/issues/21 (https://gitlab.com/inkscape/inkscape-vectors/general/issues/21) All are welcome. We hope you'll join us! -- Ryan Gorley Founder + Creative Director https://dijt.co (https://dijt.co)

1 1

Symbol edition and reuse
by Xaviju Julián 22 Oct '17

22 Oct '17

Hi, As suggested in the new features section I'd like to see the community opinion on a possible feature suggestion. As a heavy user of the symbols feature for web design I tend to save many UI portions of my design as symbols and reuse them across many different documents. Sometimes I need to edit one of those symbols and I'd like all documents that are referencing that symbol to update. Same behavior as when I update the original symbol SVG code, all references will keep using that symbol, but updated. Right now, the only way I found the inkscape UI has to edit a symbol is to `unplug` (sorry don't know the english word) it from its reference, but that does not allow me to reuse and update. Do this make sense to you? Am I missing something? Thanks, Xavi

3 2

misunderstood tiled clones issue
by brynn 08 Oct '17

08 Oct '17

Hi Friends, Someone recently has posted in a forum, asking why the first array created by Tiled Clones dialog is deleted, when the 2nd array is created (using the same parent object). http://www.inkscapeforum.com/viewtopic.php?f=5&t=33037 Because this is what I previously understood the Remove button is supposed to do, I thought it must be a bug. However searching LP has not turned up any existing bug report (not unless its title contains technical language that I don't understand, or that doesn't really describe the issue). I'm on Windows, but other operating systems are represented in the forum topic. I tested going back to version 0.47.3, and the same behavior is seen there. So since it seems to be long standing, and not reported, I have to think it's either intended behavior, or at least not a bug. Oh interesting! It seems the first array is deleted /whenever/ a 2nd array is created with the same parent (not just when the 2nd array immediately follows the first)! Because I did this (with all default settings): 1 - Object A: 2 x 2 array 2 - Move all the clones away from the array area (to easily notice that they are deleted when the 2nd array is created, and not just covered up by the 2nd array). 3 - Object B: 3 x 3 array 4 - Object A: 4 x 4 array -- This removes all the clones from the 2 x 2 array of object A; leaves the 3 x 3 array of object B alone, and creates the new 4 x 4 array of object A. If there's a reason for this, could someone explain, in a not too technical way? Thank you very much, brynn

1 0

Re: [Inkscape-user] [Inkscape-devel] the Scale setting and Display units
by brynn 27 Sep '17

27 Sep '17

Sorry I was unavailable for all this discussion the last couple of days. (just a bit out of sorts) I completely understand that everyone has different preferences for whatever project they use Inkscape to accomplish. I would say that as far as Inkscape is concerned, none should be considered better or more preferred than the other. I think it would be a mistake to force one or more user groups to always change their docs, or make their own special templates, just so that one or more other user groups can have convenience. Especially with this new system which is so confusing for many users. Inkscape should be made usable, equally as possible, for all user groups. The bottom line (at least for me) is that there is no way to satisfy everyones needs at the same time. What is needed is a simple way for users to choose and set their desired units, no matter which kind of document or template they want. Before 0.92, it was very, very simple, and easy to understand and easy to use. Now, it is not. If there is some reason related to Inkscape's being able to function at all, where mm Must be the default units, then please make Inkscape do all the work, so that the user only has to click once to change their units (as before). (Make Scaling silent.) However, I think it would be better to go back to the traditional system of px for the user units, where if a user wants to change their units, they just have to click once. > So it would be very nice to have px as the default template and let our users change units in the display as desired without any concerns regarding scale. Ditto! As a footnote, this is one of the many issues we are seeing with users not understanding the scale (it's an old topic where a new message was posted, starting here) http://www.inkscapeforum.com/viewtopic.php?f=5&t=17182#p101060 Here, it seems setting the wrong scale is exaggerating the expected deformations of paths when using offsets. All best, brynn PS - I made the wishlist report, for what it's worth: https://bugs.launchpad.net/inkscape/+bug/1719162 -----Original Message----- From: TylerDurden Sent: Saturday, September 23, 2017 9:46 PM To: inkscape-devel(a)lists.sourceforge.net Subject: Re: [Inkscape-devel] [Inkscape-user] the Scale setting and Display units >>[Luca] I ask again: is this just a template issue? << Yes, I also think so. I currently instruct all my Inkscape students at the local makerspace to create a custom default template with units=px and scale=1. Slide from the class: https://dl.dropbox.com/s/8ydap6q59dtne1i/Inkscape_Class_101-Default.png At the makerspace we regularly use px, imperial and metric; and output from Inkscape for print, CNC, laser, game design, web, CAD, and on, and on... So it would be very nice to have px as the default template and let our users change units in the display as desired without any concerns regarding scale. Thanks, TD -- Sent from: http://inkscape.13.x6.nabble.com/Inkscape-Dev-f2781808.html ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Inkscape-devel mailing list Inkscape-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel

3 5

Inkscape 0.92.2 not building
by Alice Wonder 26 Sep '17

26 Sep '17

I hope this isn't better suited for the devel list, but I'm not an Inkscape developer. Trying to build Inkscape 0.92.2 and it seems to not like ImageMagick 7.0.7 patch 4 (the current) The build error: make[2]: *** [src/CMakeFiles/inkscape_base.dir/extension/internal/bitmap/channel.cpp.o] Error 1 make[2]: *** Waiting for unfinished jobs.... /builddir/build/BUILD/inkscape-0.92.2/src/extension/internal/bitmap/crop.cpp: In member function 'virtual void Inkscape::Extension::Internal::Bitmap::Crop::applyEffect(Magick::Image*)': /builddir/build/BUILD/inkscape-0.92.2/src/extension/internal/bitmap/crop.cpp:27:78: error: no matching function for call to 'Magick::Geometry::Geometry(int&, int&, int&, int&, bool, bool)' image->crop(Magick::Geometry(width, height, _left, _top, false, false)); ^ /builddir/build/BUILD/inkscape-0.92.2/src/extension/internal/bitmap/crop.cpp:27:78: note: candidates are: In file included from /usr/include/ImageMagick-7/Magick++/Drawable.h:28:0, from /usr/include/ImageMagick-7/Magick++/Image.h:17, from /usr/include/ImageMagick-7/Magick++.h:12, from /builddir/build/BUILD/inkscape-0.92.2/src/extension/internal/bitmap/crop.cpp:15: /usr/include/ImageMagick-7/Magick++/Geometry.h:119:5: note: Magick::Geometry::Geometry(const RectangleInfo&) Geometry(const MagickCore::RectangleInfo &rectangle_); ^ /usr/include/ImageMagick-7/Magick++/Geometry.h:119:5: note: candidate expects 1 argument, 6 provided /usr/include/ImageMagick-7/Magick++/Geometry.h:52:5: note: Magick::Geometry::Geometry(size_t, size_t, ssize_t, ssize_t) Geometry(size_t width_,size_t height_,::ssize_t xOff_=0, ^ /usr/include/ImageMagick-7/Magick++/Geometry.h:52:5: note: candidate expects 4 arguments, 6 provided /usr/include/ImageMagick-7/Magick++/Geometry.h:49:5: note: Magick::Geometry::Geometry(const string&) Geometry(const std::string &geometry_); ^ /usr/include/ImageMagick-7/Magick++/Geometry.h:49:5: note: candidate expects 1 argument, 6 provided /usr/include/ImageMagick-7/Magick++/Geometry.h:46:5: note: Magick::Geometry::Geometry(const Magick::Geometry&) Geometry(const Geometry &geometry_); ^ /usr/include/ImageMagick-7/Magick++/Geometry.h:46:5: note: candidate expects 1 argument, 6 provided /usr/include/ImageMagick-7/Magick++/Geometry.h:43:5: note: Magick::Geometry::Geometry(const char*) Geometry(const char *geometry_); ^ /usr/include/ImageMagick-7/Magick++/Geometry.h:43:5: note: candidate expects 1 argument, 6 provided /usr/include/ImageMagick-7/Magick++/Geometry.h:40:5: note: Magick::Geometry::Geometry() Geometry(); ^ /usr/include/ImageMagick-7/Magick++/Geometry.h:40:5: note: candidate expects 0 arguments, 6 provided make[2]: *** [src/CMakeFiles/inkscape_base.dir/extension/internal/bitmap/crop.cpp.o] Error 1 make[2]: Leaving directory `/builddir/build/BUILD/inkscape-0.92.2' make[1]: *** [src/CMakeFiles/inkscape_base.dir/all] Error 2 make[1]: Leaving directory `/builddir/build/BUILD/inkscape-0.92.2' make: *** [all] Error 2 Any ideas?

2 2

the Scale setting and Display units
by brynn 26 Sep '17

26 Sep '17

Hi Friends, Sending up a signal flare from the not-so-technially-inclined user community. Please either explain the Scale setting and how users can easily change the Display units; or fix the UX so we can use it. Thank you so very much, brynn

5 14