Re: Digest for electricvlsi@googlegroups.com - 3 updates in 2 topics

[Alexandre Rusev]

Thank you a lot!

Verified fix, works for me in v.9.0.8

Alex

On Wed, Oct 21, 2020 at 9:30 AM <electr...@googlegroups.com> wrote:

electr...@googlegroups.com

Google Groups

Topic digest
View all topics

• com.sun.electric.tool.user.tecEdit.Exmple.getExamples(...) - 2 Updates
• Digest for electr...@googlegroups.com - 1 update in 1 topic - 1 Update

com.sun.electric.tool.user.tecEdit.Exmple.getExamples(...)

Alexandre Rusev <cybe...@gmail.com>: Oct 20 12:11PM +0300 >There are two main threads in Electric: the user and the database server. When you run code that generates circuitry (such as making a library >from a technology) then you are in the Server thread, which cannot directly invoke user interface operations. A simple test for whether this is >the server thread should be done in TechConversionResults.showError() and if so, it should report the problem but not highlighting it.     Ok. Thanks.   I still think that we can ignore some nonecritical errors when converting imported from XML technology to library for editing. And ... report errors later in user thread and post them to log window. Is it correct approach?       On Sat, Oct 17, 2020 at 7:13 PM Steven Rubin <str...@staticfreesoft.com> wrote:

Steven Rubin <str...@staticfreesoft.com>: Oct 20 04:10PM -0700 The latest changes to the repository now detect a server job and avoid the crashes that happen when a bad technology is converted to a library.      -Steve   On 10/20/2020 2:11 AM, Alexandre Rusev wrote:

Back to top

Digest for electr...@googlegroups.com - 1 update in 1 topic

Alexandre Rusev <cybe...@gmail.com>: Oct 20 12:28PM +0300 >It looks like you are using the "convert technology to library" feature >here:   >https://staticfreesoft.com/jmanual/mchap08-02.html <https://staticfreesoft.com/jmanual/mchap08-02.html>   Yeah, right.   >The error message you're getting seems to be a bug in LibToTech.java, >emanating from this line:   >error.markError(null, np, "No highlight layer found");   I found a way to ignore this one (and some other nonecritical) errors in code of LibToTech. But when ignoring errors without of setting error status user looses opportunity to know that things went wrong. So I didn't suggest any patch at my first attempt, sorry.   Yet I did a temporary fix for my self which just ignores all errors and took a look on SkyWater130 converted to library :)   >I could try to fix the bug in LibToTech, but I don't know if that's Okay, now I know it's a bug to be fixed. But not anintentionally implemented feature. >such a great use of resources. The skywater130.xml technology is >generated by a Java program; you shouldn't edit the XML file with a I saw that ;) >generates the XML file instead. It's much easier to read because Java >code can factor out repetition using loops and subroutines; XML can't >do that. Thought coding java is much more convinient for me too. The final user will typically want to take a look on technology definition when having some problem with layout drc/vls or either. In situation when I do not understand how tech layers and connectivety rules are set, I also wanted to just see it without real editing.                 On Tue, Oct 20, 2020 at 9:31 AM <electr...@googlegroups.com> wrote:

Back to top

You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page. To unsubscribe from this group and stop receiving emails from it send an email to electricvlsi...@googlegroups.com.