Suggestions from Paul

[GoogleCodeExporter]

Alpha 3.0.4

1. Rotating a pot 180 degrees results in a misdraw.

2. For ICs (probably elswhere, row spacings can be made so small only pins are 
showing. It can also be made negative, which results in a component misdraw.

3. Setting project grid spacing too small (I think sub-1mm) causes a hard 
crash.  

4. Similar hard crashes occur when setting element spacing too small in vero 
boards, etc. so this seems to be a general problem.

5. Picture placement and scale to small size seems to cause hangs. Have tried 
so far only with a png.

6. Clicking on a "new project" item only changes its component value, not the 
value of the text, which must be changed from the Edit Project. This is 
counter-intuitive. Nobody cares what the component number is for an annotation 
or comment.

7. Passive component thumbnail drawing for radial cap is confusing as it is 
solid blue. Can it have the light blue interior like the full-size ones please?

8. The boards being allowed to shrink to a point then disappear bug is back.

9. Crazy feature request... if I click on an item in the BoM, can it select 
that item?

10. If I click to select a component, but then change my mind and go instead to 
another tab, it changes to the new tab ok... but if I then go to the main 
canvas it is still showing the old component. Clicking to a new tab before 
completing component placement should abort component selection.

11.  Why did you get rid of thumbwheel zooming? That is way more awesome and 
useful than scrolling. Thumbwheel scrolling sucks, because there are two 
dimensions in which you scroll, and you usually need to scroll left to right, 
not up and down anyway.  At the very least, make thumbwheel zoom a 
ctrl-thumbwheel combo or something.

12. Once I've made the canvas big, it won't let me then reduce the project size 
to levels that should be allowable, even if there are no objects outside the 
area I want.

13. When exporting to PDF or PNG, any chance of having a rectangle frame placed 
corresponding to the document size?

14. "Bring to front" doesn't actually bring to front, it seems to be bringing 
it forward in the layer hierarchy... it often takes several applications of 
"Bring to front" to get something TO the front. Most apps have separate 
controls for bring to front/send to back and move up/down layer.

Cheers,

Paul

Original issue reported on code.google.com by pmfawc...@gmail.com on 29 Jan 2011 at 4:09

[GoogleCodeExporter]

Thanks for comments Paul.

2-5: I'll try to add some sort of validation in the component framework, for 
now I rely on users' common sense :)
6: I don't follow this. What do you mean by project's component value?
7: yes, electrolytic is still not finished. Component is missing the polarity 
marking and the icon is not done yet.
8: I couldn't reproduce this. You can shrink the board to a line, but you can 
always bring it back.
9: this is potentially hard to do. Component framework doesn't allow that kind 
of stuff and could be confusing. BOM contains nothing but the component list. 
If it takes the selection to other component any time you click on it, it can 
never be selected itself and it won't behave as other components. I was 
thinking about adding a collapsible project explorer, similar to the one in v1 
that would select a component on the layout when selected in the list.
11: it's configurable, I just didn't get to make a GUI that allows you to 
configure it :)
12: does it throw any exceptions? App log would help.
13: that could be done.
14: yes, each component has it's range of z-axis movement. For instance you can 
never make a board go in front of a resistor. I was going to add a special 
component category for stuff like image, label and similar that would be 
allowed to freely move between the layers.

Cheers

Original comment by bancika@gmail.com on 29 Jan 2011 at 6:27

[GoogleCodeExporter]

Original comment by bancika@gmail.com on 31 Aug 2012 at 2:01

• Changed title: Suggestions from Paul