asdasdasd
Update all messes up "flipped" components
Hello, I discovered some behavior of the schematic capture tool that might lead to serious errors. Twice rotating by 90° a component is preserved by "Update all". Flipping the component, which actually results in the same is undone by "Update all". So if you place an LED from the library with cathode left and anode right, you flip it (because it fits your schematic best in that way), doing an "update all" will restore the original orientation of the LED. So if you didn't notice it, your LED will be wrongly polarized. As can be seen below, after execution of "update all" the flipped version is incorrect. #Schematic#
LieBtrau 2020-01-22 04:31:27 comment 3 0 Circuit Design
Make TopAssembly & BottomAssembly dependent on layer (top/bot) on which component is placed
Hello, It's not very clear what is the purpose of TopAssembly & BottomAssembly layers. These happen to be just extra documentation layers. The "TopAssembly"-layer doesn't seem to be related in any way to components on top. The same holds for "BottomAssembly" and components on bottom. These two layers might as well have been called "DocumentationX" & "DocumentionY". More relevant behavior would be that these layers would be related to the components, just like"TopSilkLayer" & "BottomSilkLayer" are. e.g. When "TopSilk"-primitives are added in the PCB-footprint of a component (PCB Libs), swapping the component from top to bottom on a PCB, transforms pads on "topLayer" to pads on "bottomLayer", "TopSilkLayer" primitives to "BotSilkLayer" primitives. Also the reference designator swaps from "TopSilkLayer" to "BottomSilkLayer" and text will become mirrored. This is expected behavior. When "TopAssembly" primitives are added to PCB Libs, moving such a component to the other side of the PCB, nothing happens with "TopAssembly" primitives. They remain in "TopAssembly", although that component could now well be on bottom side of the PCB. They behave like the documentation layer, which is not related to top or bottom. I expect that "TopAssembly" and "BottomAssembly" would behave like "TopSilkLayer" & "BottomSilkLayer". The use case is that people sometimes want to add primitives to components that should be visible on the assembly drawing (for which TopAssembly & BottomAssembly could then be used). But they don't want those primitives be visible on the silkscreen. An example of such usage can be found here. The outline and polarity marking of the LED and switch should be visible on the assembly drawing, but not on the silkscreen of the PCB. Regards, Christoph #FeatureRequests#
LieBtrau 2018-07-02 01:43:12 comment 1 0 Feature Requests
Negative text
Hello, Would it be possible to add the option in adding texts, to add them negatively as shown in the picture below? ? I have a workaround currently : add text, make screenshot, convert to black/white, import image inverted to EasyEda. #FeatureRequests#
LieBtrau 2018-07-01 19:45:17 comment 12 0 Feature Requests
Top & bottom layers are no longer selectable
A similar bug has been reported here. I recreate it here on request of Andy Fierman. I'm using EaseEDA V5.4.11 with Chrome Version 66.0.3359.139 (Official Build) (64-bit). You can see that the top and bottom layer can no longer be enabled because they are greyed out. The issue appeared when I enabled topsolder layer. I only have this problem on one project : Tileable-8x8-LED-matrix #BugReports#
LieBtrau 2018-05-03 01:31:22 comment 2 0 Bug Reports