-
-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add symbol preview for the library tree #135
Comments
Big improvement. I don't have to place a component and look at it's parameters, delete it and pick another.... |
The next step may be to remove the separate Qucs-lib tool, because the library tree on the left panel now has all features of this tool. |
I've not found it useful. One thing "Qucs" lacks is the ability to easily make your own libraries or edit existing ones to add new devices. I've done it manually using a text editor but it's not fun. A big stumbling block was the Qucs format for it's files. Very different than Spice models and easy to screw up. |
Yes, I have requests from other users regarding the library editor as a separate tool. It is a more complex task and the most probably will not be implemented in the near future.
Are you aware about the possibility to create libraries from the Project->Create library menu? There also exist |
I am aware of it but does it allow editing or adding components? Qucsconv in Qucs is abysmal. It fails more than 50% of the time. Even when you think it works, it sometimes has missing or corrupted devices. I always ended up using the Qucsconv in QucsStudio then edit the sch in a text editor to work in Qucs/Qucs-S. The most recent version of QucsStudio 4.2.2 has altered the sch file format so much it takes far too long to edit the files to be worthwhile. |
Yes, currently there is no way to edit the library except using the text editor. The library editor tool would resolve this task. |
So one generates a "lib" for each device then splices them together using a text editor? |
I did a test of making a library. Got a weird error. R3 has no digital model. Why R3? |
No, Qucs-S can combine the models from all subcircuits in project into one library. It's not need to combine it manually.
This error could be ignored. The library generation procedure was inherited from Qucs that tries to generate digital model for all devices. The resulting |
Are you going to add Qucsconv to Qucs-S? Here is Qucsconv from one of the Qucs 0.0.20 builds. I tested it on a few Op Amps. For whatever reason Qucs 0.0.20 for Windows and the source has disappeared from the web. It has a number of new components that are useful like Cq and Lq. I have a few Qucs 0.0.20 nightly releases but I cannot say what is different. |
Well Qucsconv is a massive failure. Converted 11 Op Amps and made a library, OpAmp.lib. Only the 2 NE5532s in the library worked. Pretty much mirrors my experience with Qucsconv. I used Op-Amp_Model_Test.sch to compare the "schematic" version of the Op Amps with versions in the library I created. |
Qucsconv has several limitations. For me it works only for library containing modelcards |
Is there a way I can test the nightly release? |
I can prepare a Windows build from the latest development state and share the portable package with you in the next week. I am planning also to add component search feature before preparing a beta package. |
Suggested by @tomhajjar See #92 (comment) for context. Adding symbol and device info preview may improve the application usability.
The text was updated successfully, but these errors were encountered: