No PCB preview when ordering from EasyEDA
Hey, since months when I order PCBs directly from within EasyEDA (web) I always get "no image" as PCB preview in my shopping cart and even later in the order history. If I download the gerber zip from EasyEDA and upload them to JLCPCB the preview works fine. #BugReports#
Pockets / Z-Milling support for regular PCBs?
Hey, I'm wondering, does JLCPCB support milling pockets / z-milling on regular prototyping PCBs? I'm talking about pockets into the PCB, like a cutout, but not going all the way through the PCB. e.g. on a 1.6mm PCB I want a 3x3mm square pocket milled 1mm deep into the top side. If yes, how would I denote that? Design it like a cut-out, but add a note to document layer and order? What would the limitations (e.g. router radius) be? Same as for cutouts? Only from one side? #PCB#
Wrong board outline in 3D viewer (virtual outline thickness)
Hey, I found that the 3D Viewer is showing the board outline wrong. Instead of cutting the board in the center of the board outline track, it cuts it at the inside edge of a virtual 0.3mm wide outline, so it removes 0.15mm too much on each edge. The 2D viewer is fine. Of course this is only noticeable on small board outline features. The actual width of the board outline track doesn't change the 3D viewer, I've tested that. #BugReports#
Isometric projection in 3D view
Hey, it would be nice if the 3D view had an option for Isometric projection and buttons to adjust the view to straight top/bottom/front/back etc. view. This would allow for exporting nice pictures of the PCB for documentation and manuals. #FeatureRequests#
SVGNode Support on inner layers
Hey, a user of my SVG Import Extension noticed that inner layers don't support Images / SVGNodes. While I do get the intention behind this (after all this is designed for Images an they are usually visible) I don't really see a reason to not support it. There obviously may be reasons why someone would import an image to inner layers. I don't think this requires a huge change, so could you consider supporting it? Thx! #FeatureRequests#
i18n not working properly in extension menu
Hey, in extension menus the i18n support is not working for the extension title itself and for the tooltips of the menu items. Edit: The tooltip of the extension name itself (first screenshot) is only translated correctly when the language is switched dynamically. After a reload it defaults to english. #BugReports#
Extensions: Remove Down-Arrow from Menu
Extension Menus do have a Down-Arrow by default. I guess this is a relict from the past when EasyEDA and also Extensions just had Icons in the main menu. The Down-Arrow should be removed, it makes no sense... Maybe also seperate Extension Menus with a vertical divider from the regular Menu items. #FeatureRequests#
API: createShape is missing shapeType SVGNODE
Hey, for https://github.com/xsrf/easyeda-svg-import I'm currently using getSource / applySource to add shapes to the editor. I now wanted to use createShape instead. While this works fine for the import of TRACK, it doesn't work for SVGNODE. The code is actually missing the SVGNODE in the list of types. If I add it manually to o, it works. #BugReports#
API: let user place created shape
Hi, I want to suggest to provide an api that lets you create a shape and let the user place it (the same way when you place a part). When I use api('createShape',...) I have to specify the coordinates where the shape is placed implicitly (for svg path based objects) or explicitly. For SVGNODES I can use importByPathD which lets the user place the shape (however, it will place the shape again and again until the user aborts), but I haven't found an easy way for other shapes. My current workaround for that is a real hack :D I create the shape at the left top of the editor, get its id (which also requires a workaround), select it, call cut, fake a click event at the left top to set the reference point and call paste. It works however ;) It would be great if createShape had options to allow letting the user place the shape (once or multiple times) optionally with a way to set the reference point. #FeatureRequests#
API: id of shape created via createShape
Hi, is there an easy way to get the id of a shape added to the editor via api('createShape',...)? My current workaround is to get all ids from the project source json before and after calling the api and subtracting them from each other. I'd suggest that api('createShape',...) could just return the ids of the shapes created, if I didn't miss anything. At the moment it returns nothing... #FeatureRequests#
Changing height of text with unknown font redraws it without asking
Hey, when I have a text with an unknown font, I can still rotate it, mirror it, change layer etc. When I try to edit the text itself, EasyEDA tells me that this is not possible without drawing it with another font and I can cancel the change. However: When I change the height of a text with an unknown font, EasyEDA just redraws it with the default font immediately. EasyEDA should also ask me if I want to proceed in this case. #BugReports#
API: Access to installed fonts / opentype.js Font Object
Hey, is there an easy way for an extension to get access to all fonts (the indexDB only has the ones installed by the user, not the default ones) either as ArrayBuffer or better as an Font instance of the opentype.js you are using to parse the fonts internally? #GeneralDiscuss#
[SOLVED 6.4.17] API pathToPolygons returns coordinates in different formats
Hey, I just found out that pathToPolygons is available via the API and I'd like to use it for https://github.com/xsrf/easyeda-svg-import/issues/9 api('editorCall', { cmd: 'pathToPolygons', args: ['M 0 0 C 1 1 2 1 3 0']}) However, it returns the first and last coordinate as Array of two strings, while the rest are Objects with x/y coordinates. I came across this earlier but didn't know what caused it. Is there a reason for this? Is it a bug? It obviously works, but... I can use pointArr.map( p => (p.x == null) ? { x: p[0] , y: p[1]} : p ) to correct it but I'd like to know why I have to do this or if I may run into issues when I correct the first coordinate to x/y... It worked for me so far. Edit: Moved Topic to "Bug reports" because I think that's not the expected behavior. Someone may still correct me ;) #BugReports#
Adding an Icon to PCB Toolbar
Hey, I've just hacked together a new extension: https://github.com/xsrf/easyeda-toggleview Rather having a menu item for it, I'd like to have an additional button in the PCB Tools Toolbar. I think this was possible when I first looked into the API few years ago but it doesn't seem to work anymore. Of course I can add an icon "by hand" with the full dom manipulation, but I'd rather do it via an official API. Is there a way to do this? #GeneralDiscuss#
valConvert error: getPCBUnit is not defined
Hey, api('valConvert', {type:'real2canvas',val:'20mil'}) throws an error: Uncaught ReferenceError: getPCBUnit is not defined Reference: https://docs.easyeda.com/en/API/3-API-List/index.html#Value-Convert#Bug Reports#
API: How to update a progress bar?
Hi, how do I update the value of a progress bar? // Test #1 x = $.messager.progress({ title: "Processing", value: 5, text: "{value}%", interval: 0, closable: true }); x.progressbar(); x.progressbar('setValue',50); // Test #2 x = $.messager.progress({ title: "Processing", value: 5, text: "{value}%", interval: 0, closable: true }); x.progressbar({value: 50}); Both kind of work but mess with the layout... #GeneralDiscuss#
Support for M(ove) in SOLIDREGION in PCB Editor
Hi, since EasyEDA struggles with SVG import I'm currently writing my own SVG import that converts SVG to SVG Nodes or SOLIDREGION Nodes. While SVG Nodes work fine with complex shapes, SOLIDREGION has problems as soon as more than one closed path / a M(ove) command is within the region. EasyEDA is not able to drag / move SOLIDREGION Nodes that contain a M(ove). Within the GUI it looks like it moved the region, but it throws an error in the console and when you reopen the project the region is back where it was after the import. However, even complex shapes seem to render fine when creating gerber files. So the region actually works. So, can you please add support for more complex solid regions that contains moves? This is essential for regions with cutouts because these cannot be split into separate regions! Thx #FeatureRequests#
Text on mask layer not rendered properly in gerber viewer
When I add Text (or other SVG artwork) on the mask layer in EasyEDA it is not rendered properly in the gerber viewer. Mostly affects shapes with voids I guess. So I'm not sure what I'll get when I order. Example: #BugReports#
Board outline not detected if only top/bottom layers are used
When I only use top/bottom copper/mask layers in EasyEDA, the board outline is not detected by the JLCPCB order preview and gerber analysis. Also, if the mask layer is empty, the mask is not shown on the order preview. I have to add a hole/via/th-pad inside the board outline for it to work. Example: #BugReports#
SVG Import performs really bad
Hey, I want to import a geometry created with OpenSCAD to my PCB as Silkscreen/Soldermask layer. I can export as DXF or SVG. When I import the geometry as DXF the geometry is spot on, but filled areas aren't filled anymore. When I import as Image (SVG), the filled areas are filled, but the geometry is a mess. Is this a bug? If not - how else can I import the geometry? Thx Edit: Looks like I can't post the SVG in Code-Tags... #BugReports#
How to link SCH Symbol to footprint from a PCB Module?
Hi, I've added a PCB Module to my PCB that contains two footprints for Headers\, prefixed REF1 and REF2 and named PIN_HEADER_STRAIGHT_2X09_PITCH2.54MM and PIN_HEADER_STRAIGHT_2X20_PITCH2.54MM. In my SCH I've added also two Headers\, prefixed them REF1 and REF2 and in the Footprint Manager I've selected PIN_HEADER_STRAIGHT_2X09_PITCH2.54MM and PIN_HEADER_STRAIGHT_2X20_PITCH2.54MM for the symbols. When I then click "Import changes" on my PCB, it will remove REF1 and REF2 and then add REF1 and REF2 and reposition them... The original position of the headers will get lost (which is a problem). Why won't it just update REF1/REF2? How do I properly link an existing footprint on the PCB to a SCH symbol? #GeneralDiscuss#
API Error: extId is required on createCommand
Hi, I wanted to try to create an extension, but I ran into the error "extId is required" as soon as I call api('createCommand', { ... }). I copied the code fromhttps://github.com/dillonHe/EasyEDA-Documents/blob/master/API/example/theme/main.js and pasted it into Tools -> Extensions -> Run Script. Also tried this simple code in Tools -> Extensions -> Run Script: api('createToolbarButton', { title:'Shape', fordoctype:'pcb', "menu" : [ {"text":"Log Selection", "cmd":"extension-debugshape-log"}, ] });``api('createCommand', { 'extension-debugshape-log' : function() { console.log(api('getSelectedIds')); } }); Toolbar button shows up, but same error on createCommand Since I found no documentation ... what is wrong? #BugReports#