On 1/29/07, Andrew Mellinger <andrew@...2091...> wrote:
> I've been trying this with patterns and cloning and I have problems with
> bounding boxes. It looks like the tiling wants to tile base on bounding
> box, but the box is outside of the actual area by some amount like the
> size of miters, or lines or soemthing. i.e. The bounding box doesn't
> bound to the node points, but to the line. This makes it impossible (as
> far as I can tell) to make a pinstripe pattern.
So, does Freehand ignore stroke when displaying bounding box?
I'll need to find a version of classic to fire up to get FH8 working.
The big thing is that I don't really remember being that aware of the
bounding box in FH8. By being aware I mean it was never an issue or
impacted my drawing. Let me give you an example:
I have two rectangles with large strokes and I'm using grid snap. When
I drag them side by side so that two edges align the grid snap has those
two edges overlap. Thus you have a wide rectangle with a single line
down the middle, but the line is the normal stroke width.
That frustrated me about Inkscape at first, until I turned off bounding
box snap and turned on node snap.
thinking about providing this as an optional mode too, so if it does,
it will be another reason to do so. The stroke-inclusive bbox is
better for artistic uses and for newbies, but technical users seem to
prefer a bbox without stroke.
When it really gets right down to it, I don't care too much about
bounding boxes, I just wanted to get the pattern/clone issue to work
right. I suppose my ultimate desire is that things follow the principle
of least astonishment. Thus if I draw a line diagonally across a grid
cell then tile it or pattern it, I expect it to basically fill the other
adjacent grid cells identically. I suppose that is the easiest way to
explain my expectation. But I'm fully aware that this may not be what
normal people do. ;)
Also, we don't have many Freehand users on this list, so I would
really welcome any feedback you can give about Inkscape from the
viewpoint of a Freehand user. What features are you missing the most?
What UI elements you hate/love the most? etc.
It has been a while since I've used it heavily, I'll try to refresh
myself and provide some better input.
What I miss the most is the duplicate command that remembers offsets.
In FH8 it would work like this: Duplicate and the new item is place at
some x,y offset. (Which is configured in user prefs.) The duplicate
object is automatically selected. If the duplicate is moved (e.g.
draegged) somewhere, then the duplicate command is done again, the third
object would have the same offset relative to the second that the second
currently has the first. This makes it really easy to create copies
with arbitrary spacing. This wouldn't be too hard to do in Inkscape.
If the clone option simply created the next clone at the difference
between itself and originator, you'd have the same effect. And it would
be a lot faster / more intuitive than the clone dialog. Maybe it does
this now, but I didn't think so. I'll go back and check. Maybe I'm
thinking of duplicate doesn't do this.
Another thing I miss is the idea of 'last defaut' vs current object
prefs. Let's say I create a new box, then bring up the fill/stroke
dialog and set the stroke dash style. Then I draw another box.
Normally I expect the next box to follow a default not the one I just
modified. If I don't have any objects selected when I call up the
frame/set (object info in other apps) then I can modify the 'defaults'
for the tool. This is also done in OmniGraffle. They go as far as to
make the tool selection be a popup menu that retains the most recently
used styles. This is a lot more work and can be handled more easily
through just keeping a lot default objects around and copying them so
isn't that big of a deal.
I remember also that some app (I'm pretty sure FH8) had the ability to
option (alt) click on objects to select the one beneath. I couldn't
find that in Inkscape. This is great if you have a lot of stacked
objects and need to work down thorugh the stack. Just keep option
clicking down until you get the one you want. Of course this feature
may be there, I just didn't see it.
BTW: The little modifier key tooltips at the bottom of the window
As for your problem, in the clone tiler you can set any interval
between clones, including a negative interval which can be set to
negate the stroke width.
I will try this and the ideas for removing the stroke and see which is
easier! I'm sure one of these will work. Thanks!
From MAILER-DAEMON Tue Jan 30 12:41:07 2007
Date: Tue, 30 Jan
2007 21:40:29 +0100
From: Thorsten Wilms <t_w_@...1631...>
User-Agent: Mutt/1.5.13 (2006-08-11)
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net
for more details.
Report problems to
Subject: Re: [Inkscape-user] Layers dropdown
Inkscape User Community <inkscape-user(a)lists.sourceforge.net>
List-Id: Inkscape User Community <inkscape-user.lists.sourceforge.net>
X-List-Received-Date: Tue, 30 Jan 2007 20:41:08 -0000
Content-Type: text/plain; charset=us-ascii
On Tue, Jan 30, 2007 at 11:59:36AM -0800, Bryce Harrington wrote:
But this makes me wonder if the status bar could benefit from some
of adaptive ui behavior or perhaps just a configuration setting? For
new users, the layer dropdown (among other things) could initially just
be scary clutter, so clearing off the status bar in favor of status
messages could make the application >look< a lot more approachable.
Then, later once they've gotten more comfortable, they could graduate
into expert mode and have these extra accessories turned on.
All texts I ever read regarding usability that touch this topic
advice against such modes.
- Implementation effort
- Options need to go somewhere
- Need to be documented
- Related to the 2 above: discoverability. It's not likely
that you find what you didn't look for. Forming expectations
and searching for features is extra work.
- how is a user supposed to know when he's ready for any kind of
- if the app tries to judge the user, it can only fail and
will appear unpredictable.
- if you change any behaviour, user has to learn again.
/me rereads ...
Well, so much on modes and adaptive behaviour :)
Just having show/hide for some more stuff should be ok.
Always opens the question what to show per default.
I don't care about pointer coordinates ... but they don't
bother me so that I didn't even check if I can hide them