Tom
08-24-2002, 09:45 AM
This is the first PowerPCB V5.0 bug we've encountered. It's repeatable. Open a blank database to try this. (Do not try this in a real PCB design file) Go to the Drafting Tool Box and select the Copper ICON. Then RMB (Right Mouse Button) and select Rectangle. Enter a large "snap grid" to make it easy. Click to enter the copper rectangle, but instead of creating a rectangle try to create a path by selecting two similar "Y" coordinates. You will get a PowerPCB "Warning" message that states "Self-Intersecting Polygon". This is the correct response.
Now try the same thing with Board Outline, Keep Out, 2D-Line and Copper Pour. V5.0 actually allows the creation of a rectangle even though you selected the same "Y" coordinate. Then try to Zoom In and Out. They do not go away. Then try to select and move the Keep Out. V5.0 allows the move but gives you an error message "Self-Intersecting Polygon" when you place it down. When you move the 2D-Line you do not get any error message. When you move the Copper Pour V5.0 will not allow you to select it unless you window around it and you do not get an error message. When you move the Board Outline it vanishes (disappears) from your database graphically (after you refresh) but it is actually still in your database. Try inserting another Board Outline and you will get the message "Board Outline Exists".
Next, delete all the objects and select File / Export / ASCII / All Objects / Current Units and you will get an error message.
Then try to import that ASCII file and you will get another error message and the Board Outline will appear again. Try to move it and it vanishes again.
In PowerPCB V4.0 every time you tried inserting any of these Drafting objects, you always got a "Self-Intersecting Polygon" error message. V4.0 would not allow you to insert a Rectangle unless you selected different "X" & "Y" coordinates.
The work around here is "Just don't do it". This is just a notification to make you aware to avoid doing this. We have not noticed any database corruption or any other harmful side affects (so far) as long as you delete the object. We have classified this as a non-critical bug.
We haven't found any other bugs or problems with V5.0 yet. We are moving forward with the implementation of V5.0 in our production environment. The new features greatly out weigh this minor problem (which will be fixed in V5.0.1) coming out in October/November.
We have notified tech support of this problem and we are waiting for a Bug Tracking Number.
Now try the same thing with Board Outline, Keep Out, 2D-Line and Copper Pour. V5.0 actually allows the creation of a rectangle even though you selected the same "Y" coordinate. Then try to Zoom In and Out. They do not go away. Then try to select and move the Keep Out. V5.0 allows the move but gives you an error message "Self-Intersecting Polygon" when you place it down. When you move the 2D-Line you do not get any error message. When you move the Copper Pour V5.0 will not allow you to select it unless you window around it and you do not get an error message. When you move the Board Outline it vanishes (disappears) from your database graphically (after you refresh) but it is actually still in your database. Try inserting another Board Outline and you will get the message "Board Outline Exists".
Next, delete all the objects and select File / Export / ASCII / All Objects / Current Units and you will get an error message.
Then try to import that ASCII file and you will get another error message and the Board Outline will appear again. Try to move it and it vanishes again.
In PowerPCB V4.0 every time you tried inserting any of these Drafting objects, you always got a "Self-Intersecting Polygon" error message. V4.0 would not allow you to insert a Rectangle unless you selected different "X" & "Y" coordinates.
The work around here is "Just don't do it". This is just a notification to make you aware to avoid doing this. We have not noticed any database corruption or any other harmful side affects (so far) as long as you delete the object. We have classified this as a non-critical bug.
We haven't found any other bugs or problems with V5.0 yet. We are moving forward with the implementation of V5.0 in our production environment. The new features greatly out weigh this minor problem (which will be fixed in V5.0.1) coming out in October/November.
We have notified tech support of this problem and we are waiting for a Bug Tracking Number.