DrPocter

Hi Meb, Thanks for your reply and for your tips. As a matter of fact I already use slices to export assets for web design projects (and they are great). But I still have the problem (not limited to web design) where I want to remove the superfluous, repeating pixels on the edges of an image. As the (or maybe just my?) artwork often blends into a background, it's not always easy to see where that boundary is. But it would be easy for an algorithm. I don't need an elaborate dialog à la Photoshop either. Just a command that trims repeating lines of the same colour (or transparency, but that already exists if I understand correctly) at the four edges of an image.

I really could use a Trim command as well. Especially in web design, where you want the smallest image possible to, say, blend into a background of the same colour.

No worries, Matt. Keep up the good work.

Ah, Marmite. You either love it or you hate it… :wacko:

I have the same problem. Although the expanded strokes are precise, I'm sure the same shape could be done with fewer nodes.

I agree with all of the above, but I prefer the checkbox to an eye.

Yes, I see where you're coming from, but to quote Mister Berra: “You've got to be very careful if you don't know where you're going, because you might not get there.”

Here's my vote for HUDs.

I think these guys probably really are fantastic programmers. Everything else: assumptions. It's better to release something that's almost there and then improve it (iteratively and through communicating with the users), as opposed to waiting until it's perfect and never release anything.

I don't think it's a programmer “lead” initiative. If anything, it's a “feather” initiative. I, for what it's worth, have made quite a few suggestions that didn't fall on deaf ears but, quite the opposite, got wings and are now implemented. ;)

You guys are the best.

Wow, really looking forward to that! Actually, that deserves a quote from Mister Grid himself: “The grid system is an aid, not a guarantee. It permits a number of possible uses and each designer can look for a solution appropriate to his personal style. But one must learn how to use the grid; it is an art that requires practice.” – Josef Müller-Brockmann

Rui and Gear are right. Guides should always be available.

I couldn't agree more. This should be enabled by default. And rather than adding another option in Preferences, I suggest one of the following 1 · saving the state on a document basis, or, probably better 2 · saving the state globally for the app, no matter what document is open. I prefer option 2. That way, once it's set, I'm good because that's the way I work.

I'm with Alan: Merge Down, Merge Visible and Flatten should do the trick.