@Matthias thanks for the hint. I used the default_base_path (*.lyt) of the technology object to go up to the grain.xml file. I read the version number out of the grain.xml as you suggested. It does exactly what I want. :)
I got something to work but the result could be better. For each violation I will get one category in the browser. Would be nice when I could bundle them again.
chip_frame = input(0,0)metal = input(1,0)max_density = metal.with_density(0.8 …
I found the reason. I think I cannot write in the SystemScope.
Following works correctly now.
import pyasettings = pya.QSettings(pya.QSettings.UserScope, 'MyTest')settings.setValue('test_slot', 'ABC')test = settings.value('test_slot', 'DEF')print(…
I tried it on Windows. KLayout version 0.26.4. (qt 5 python 3)
I tested it on Linux 0.26.3. (qt 5 python 3) now. I confirm it, on Linux it will prints "ABC".
Maybe a permission conflict on windows? I guess on wind…
Renaming of the "KLayout" directly solved it. Some further investigation I tried to rename the "klayoutrc" file to init a new one. This speed it up again. My new "klayoutrc" file is 13KB big instead of my old one wi…
Maybe another idea could be to include a new tag in the *.lyt file?
The tag could group them in the menu and maybe in the technology manager as nested list as well. I do not know what wo…