Designlib probing
Draws signalling charts, block diagrams and graphs from text input.
Brought to you by:
teknos293
Menu
▾
▴
#20 Designlib probing
Hi Zoltan,
Currently, a design library is 'probed' from the user's roaming profile folder. Additionally, as far as I can determine, the designlib is not re-read on modification and on Windows the file is locked for reading only. This makes changing a designlib somewhat difficult, especially when you have a number of Msc-generator windows open.
Is there a way to start the design library probing from the folder where the .block/.signalling/.dot-file resides first, then try roaming profile, then installation folder? And not lock the file and detect changes as well?
Kind regards,
Martijn
I will look into why the file is locked. However, it would require a lot of rework to detect changes to this file and re-load (re-populate the design combo boxes, etc. and re-compile) automatically. Right now I rely on the initially loaded design lib not to change on quite many places.
As a workaround I suggest you use your designs via an include file first and when they have stabilized then move them to a design lib. Would this workflow be good enough? If so, I cancel this. If not, then I will put it on a list for longer-term rewrite.
Hi Zoltan, this would be a good enough workaround for me. I believe that circumvents both the way probing currently works and the locking issue. The only difference would be that I explicitly reference this (pseudo) designlib, which is totally fine. As long as there is made no distinction between how hints/intellisense functions between included files and designlibs that is ;-)
Thanks! Also for adding the feature of highlighting the current line in the editor, such a thing might seem small, but it was actually on my wish list.
OK, then I close this. The differences between included files and the designlib are as follows:
design libs cannot contain actual chart elements, just shapes, styles designs and colors.and maybe procedures.
shapes defined in included files are not shown in form besides their name at hints (intellisense)
included files make things slower
included files may end in the middle of a definition (if the definition continues in the main file). Design libs must make sense in themselves.