PICTURES GIMP VS PHOTOSHOP HOW TO
PICTURES GIMP VS PHOTOSHOP SOFTWARE

And they do not offer solution to variant tracks. You can see that most of the solutions are a really awkward and feels more like a work-around-work-around than a proper solution.

PICTURES GIMP VS PHOTOSHOP HOW TO

For example some time ago I’ve been reading here about board variants: How to manage board variants (different components and footprints)? - #6 by poco But that is this one example and even here it adds an extra work.īut I can find more examples that could be solved easily and more intuitively by using layers. Only their behavior is so deeply engraved into the KiCad (or any other EDA) that you do not think about them like that.Īnd yeah, I can make a copy of footprints on the user layer or export it to svg and re-import or any other way I can think of.

You can think of them as collection of layers that you map onto a physical stackup.

And it is not completely true that you can not something like that. But that just means that there are limitations for what you can do with the layers or not. I do understand the concept of layers being mostly physical. In the meantime, I’d personally second the idea of additional footprints that only consist of documentation layer information just for positioning stuff. (I don’t know of anything that does this now, but maybe someone else does?) On the other hand, that might be a reasonable job for a plugin that could act like a many-item clipboard and let you “cut” out groups to plugin storage, deleting them from the board, and copy them back in later.

PICTURES GIMP VS PHOTOSHOP SOFTWARE

That’s a complex problem to solve from the point of view of the core software which really cares about what the final physical board will look like.

There may one day be a way to “hide” groups (not just from visibility, from existing on the board at all) but I’ll be surprised if that time comes soon. Groups are the best collections we have at the moment. Similarly, you can’t take a footprint with information on 1-4+ physical layers, flatten it all onto one User (normally for documentation) layer and then re-expand it. You can’t drag a layer from the bottom to the top, since that wouldn’t make any physical sense. I think one overarching issue is that most of KiCad layers are physical things, not grouping/ordering concepts like in Gimp or Photoshop.

Pictures gimp vs photoshop