Alex Lawrow

The netlist doesnt contain part footprints so wont help with optimising a layout. There are probably some more modern netlist formats that contain additional information on part sizes and design limits for PCB layout and testing. You would be best off using an EDA program that starts with circuit schematic and all the part info.

The netlist doesnt contain part footprints so wont help with optimising a layout. There are probably some more modern netlist formats that contain additional information on part sizes and design limits for PCB layout and testing. You would be best off using an EDA program that starts with circuit schematic and all the part info. VeroRoute is

There is no netlist export and no easy way to get it from a vrt. I dont see the value in having that functionality and am wondering why you would need it. May I ask what you are trying to do?

There is no netlist export and no easy way to get it from a vrt. I dont see the value in having that functionality and am wondering why you would need it. May I ask what yiu are trying to do?

There is no netlist export and no easy way to get it from a vrt. I dont see the value in having that functionality and am wondering why you would need it. May I ask what yiu are trying to do?

Nets in VeroRoute are just numbers (the things you see in the "Broken Nets" list of the control panel). They are not named, as you might find in the import file. During import, each net in the import file will be mapped to a unique net number within VeroRoute. You can use whatever part types (i.e. package names) you want in the import file so long as you set up appropriate aliases for them within VeroRoute. Unrecognised types in the import file will be listed at the bottom of the "Part Aliases" dialog,...

Force small menu font on Android to try avoid strings with ellipses. Better handle file names for Android.

This is an update to the code to support Qt6. The precompiled versions that can be downloaded here are still built against Qt5, so you will not see any significant difference between V2.40 and V2.39 other than a version number change. There are problems with my Android build of V2.40 since it uses Qt6 (and I no longer have the build tools for Android Qt5) so I will not be providing an Android package for V2.40 at the moment. Basically, the way Android handles file permissions has changed (and seems...