[sdiy] Pulsonix PCB design software

[sleepy_dog at gmx.de]

- . . . DipTrace / KiCad differences -

electronicpresskit wrote:
> One thing that irked me was that the user can change the part number of a multi-part package, however the pin numbers don’t update to reflect the change. So the user must delete the part and create a new one. This would be less of a problem, except that the wires disappear so you need to remember all the connections. I like to optimize which opamp I use depending on adjacent components when placing parts on a board so it can really add some time and increases the chance of error.

Couldn't you just select the involved parts, do "disconnect wires", then 
just swap them and do "connect wires"?

> I don’t think this method of zooming is considered broken by the kicad community.

>   I can see how it’s jarring, it probably was that way for me at first but it’s absolutely normal now.
Yes, people can get used to all sorts of (incl. dumb) things. There 
should be a good reason for it, though.
Restricting the zoom target to one point on the screen is rather 
uncommon (other than in rookie programs) - unless as a special mode, 
like explicitly restricting movement axes for a certain purpose.
I need to keep using the "hundred" other programs which zoom properly, 
and am thus unwilling to force myself to feel that one outlier is the 
normal and all others to feel weird.


>   The zooming method in dt actually bothered me a bit :) If I zoomed in on a part near the top edge of the viewable area I would often need to scroll to see what was above it.
Huh? It does exactly that - moving what you point to closer to the 
center while you zoom, which means that if you see any component 
anywhere on the screen, you point on it and zoom, then you will see its 
surroundings just fine.
Wheras KiCad can only zoom around the center, as if too lazy to 
implement proper transform.

I.e., KiCad zoom is merely a crippled version of proper zoom - where you 
can choose a point as your zoom target anywhere on screen, *including* 
the center - i.e. then do exactly what kicad would do - only that you 
are not *forced* to it.
How is this restriction a feature?

Zooming where you point to zoom allows you to actually navigate at the 
same time, like the thing grants you 3D movement with that one "analog" 
input device. Rather efficient & smooth.


[ranting again. No really, the rant starts here!]

It would be easy to let the user choose between full and crippled zoom 
mode in the options.
If the devs cared... (I seem to be not the only one voicing disapproval 
in similar matters, and not just since yesterday)

It's a common problem of open source projects. Tend to be some guy's 
hobby proj. Zero pressure to listen to users.
Good programs include options for stuff, and a lot of them.
Devs who demonstrate to not give a damn are bad omen ;-)
(I'm not saying some big names aren't feeling very comfy in their 
position and also don't give a damn about their mediocrity if their 
stuff is bought because they have been THE name for a very long time)


>   What I find useful about the kicad zoom is that you always get to see what is surrounding your point of focus.
As said, I'm not sure what you mean


> diptrace made good progress by adding user definable keystrokes but the available actions are more extensive in kicad.
Ok, but if extensive means all the lesser used things are also on keys, 
it'd not be relevant for me.
But there were a few things in diptrace where, I believe, was no key for 
and I wish there was ;)

>   It’s also that you don’t need to click on anything to perform an action. Just hover the mouse and hit c to copy something then drag and click to place. Standard copy/paste is click+modifier+c plus modifier+v to paste. Is that really one move vs five?
No, from what you listed, 2 : 5, if you need to click to place ;)
Also, counting Modifier+Key as "two" reeks suspicious. I do it in 
parallel and it doesn't feel like 2. Honest, are you cheating?
But yeah, this sounds like it could be a help, but also error prone, 
unlike when something is shown as selected and the selection can't be 
accidentally changed by slight mouse movement - I mean before the key 
engaging e.g. copy mode really registers.
I guess I'd have to try that for a while. But not with KiCad, until they 
have options for all the stupid stuff :-P ;-)


> As a point of reference, a 1300 pin schematic is 311kb.

Thanks, sounds fine, if really everything is contained in the file (no 
external references).
Hahah! Just saw I have a diptrace binary of 3x that size. Now I wonder 
what the heck is in there.