Feature Recommendation: Pertinent Help File Access to Custom CBlocks

QSPICE
1

In today’s QSpice, it has a special feature on standard QSpice components that allows the user that drops the component on the schematic to open a page specific to the component in the QSpice help file.

image
image208×130 14 KB

What if this feature be used to select a pdf file with the same CBlock name located in the same directory as the where the CBlock is being referenced? Useful?

Len

2

In my observation, .qsym files are designed to be standalone with no directory linkage. When you drag a .qsym into a schematic, the entire symbol is embedded directly into the .qsch file. Coming from LTspice, sharing schematics with custom symbols was always a pain because you had to send all symbol, its schematic or .subckt files, then ensure they were placed in the correct directories. Qspice completely solves this by embedding everything (except C++ code) into a single .qsch file, which makes sharing seamless.

That said, I agree it would be useful if .qsym files supported detailed descriptions (in additional to current single line description). Hovering over the symbol could display a formatted text box with clickable hyperlinks for further documentation based on that detailed descriptions.
OR, may be a simple hyperlink description option will help. :rofl:

2 Likes
3

@KSKelvin ,

I agree QSpice simplifies subcircuit blocks by including all the info in the schematic … except for where to find the DLL. This is handled by one of two methods:

  • The DLL is found in the current directory where the .qsch is located … or
  • The DLL is found in the .libpath statements generated by the directory tree of the "Symbols & IP Browser.

Therefore, why can’t QSpice parse the .libpaths to find name.pdf since it already finds name.dll?

Although the hyperlink suggestion sounds interesting, there are some potential issues. Such as:

  • Someone could create a dangerous link
  • The link is out of commission if:
    • The internet is down
    • The link got changed
    • The CBlock component was function updated and the help file got updated as well. However, the user is using an older version of the CBlock component.

I believe there is a big advantage of tightly associating the CBlock being used to help file info. This is best achieved by localizing the help file in the same directory as the dll.

If the user downloads a later (or earlier) version of the CBlock component, the help file attached should be synchronized.

4

Just my opinion, not have to agree with me. :rofl:

5

@KSKelvin ,

Your opinion is valued. I think we both find value in this potential feature.

A good discussion of pros and cons on implementation strategies might convince Mike to add the feature. What strategy to use? It might be what is easiest to implement in SW.

1 Like