| Thread Previous • Date Previous • Date Next • Thread Next |
jean-pierre.charras@... wrote:
Dick Hollenbeck a écrit :What happened to my nice green copper layers?I am afraid I was the culprit, but here is the reason:* the layer order for the inner layers (using the old pcbnew layer order) was the reverser order the new layer order used in the layer manager and the layer box. * So tho match the new layer order I reversed the inner layers order (easy...) Matching the layer manager order is important also to avoid mistakes when selecting layers types (this was mainly my motivation). * but after doing this, the active layers were located to the bottom of the window, and, for 2 or 4 layers board and not visible without scrolling. This minor problem also could create mistakes because when changing layers count from 2 to 4, nothing seems happen. * Easy workaround: hide not active layers (this is what I do), so only really active layers are shown, and no need to scrolling the layer list. Alas! calling wxPanel->Show(false) or wxPanel->Show(true) to hide/show items *crashes* pcbnew (I do not know why), at least under Windows, and I was unable to solve this problem. So I made an ugly change: remove the wxPanels having your nice green copper layers background. * Of course your original file is not removed: this is "dialog_layers_setup_base_previous_version.fbp.unused".
Maybe we can support the old code and new code under two sets of file names. That means restoring the *.cpp files as before. This way you only have to make an edit to your CMakeLists.txt file to select the new set while you iron out our daily Windows problems.
I had orginally assumed that the layer flipping was going to take place sooner than it has. And that due to scarce resources we would not have the time to re-do this dialog over and over again. I was leading a moving target. The target did not move, and I overshot it. So we can take another shot, or we can move the target.
All I can say is that I spent a LOT of time on that dialog, and don't want to see that time go to waste. This would be intensely de-motivating.
You are finding out now how much time I spent on it. :)Is there a FINAL solution ? No, there are two solutions, one for each layer order, now and future.
I hate to say it, but what I learned from this dialog I applied later to the LAYER_WIDGET, and one of those things I learned was that using wxFormBuilder was not practical. Having a concise, TABLE driven data definition proved to be easier. You have used the LAYER_WIDGET::ROW() structure, and see how powerful it has been.
The danger in adding and removing layer rows on the fly is that the user may spend time editing names, if he accidentally changes the layer count, he (meaning I) do not want to have to re-enter those names once I increase the layer count back to what they should be.
One thought, not a request, just a thought, is to go table driven. In the mean time we might want to restore the old code as a default and plan on a source file name change for the new code.
Dick
| Thread Previous • Date Previous • Date Next • Thread Next |
