LabVIEW
Looking for feedback on the Carya PDF toolkit.
The idea is that the free version has this text, and the professional (=paid) version doesn't. The profesional version has other extra features as well.
There will be a new version, although it keeps getting delayed. For this new version we are considering a free version withouth "teaser". The free version will be limited, the professional version will have much more functions. But for simple reports the free version can be used. We haven't decided if the free version is allowed to be used in commercial version (I think formally it's not in the current version).
New features include:
+ Encryption
+ CJKv fonts (enabling Chineese, Japanese, Korean, Vietnamese text, but also Chech, Greek, Cyrilic, etc.)
+ Changing fonts within text (using definable escape codes)
+ Graphics, including rotated text and masking
And obviously bug fixes.
What will end up in the free version is to be decided.
Regards,
Wiebe.
Search LabVIEW like a graph! >If one existed PDF can be opened? then the text will be inserted.
Existing PDF's cannot be opened at this time. The PDF specification is just to elaborated to make a "reader" for it.
Regards,
Wiebe.
Hi Giri,
Thank you for your interest.
The free version is distributed without diagrams, and can therefor not be imported by other versions.
The licensed version can be used in all versions of LabVIEW (from 7.1 or 6.5 on request).
We are still actively developing the toolkit, but maintaining the free versions just takes too much time. At some point we will provide free versions again, but to do so we need to cross some bridges before we can do so.
You could try to contact sales. Under some circumstances we can provide a temporary evaluation license.
Regards,
Wiebe.
@beuvink
Can't place that llb, what Vi should I be looking at?
C:\Windows\Fonts\BASKVILL.TTF is the default value for the input. If you don't wire anything it will look for C:\Windows\Fonts\BASKVILL.TTF...
I haven't tested it, but a descriptive error would be nice.
The VI shouldn't generate an error dialog. And it does if the file doesn't exist...
I wouldn't recommend 'fixing' VI lib VI's.
@beuvink wrote:
- placing a wrapper around 'set font.vi' in the toolkit so it refers to an font present in %windir%\fonts (this font seems to be ignored)
I don't get this at all. The font that you refer to is embedded in the PDF. You have to actually set that for for it to use. Of course the font needs to be available.
If you don't use the font you're embedding, you don't need to (and shouldn't!) use "PDF Set Embedded Font.vi". It will only make your PDF (much) larger.
See "Examples\Advanced\PDF Embedded Fonts.vi":
Hi Wiebe,
thanks for the quick reply, as always 👍
I've changed the 'Open file+.vi'. I've added a format into string in the 'build error' case in the end.
The file throwing the error dialog is 'read characters from file.vi' in the same llb. (vi.lib\Utility\file.llb). See screenshot below.
I am using the set font vi in a slightly different way. Instead of custom1 I select any of the default fonts in the Font ID enum. I do not connect the font file input (as font file availability is not stable over systems).
When the file is missing, pdf is generated fine, using the Helvetica font embedded. (acrobat->file properties). The first font fails:
If the system contains BASKVILL.TTF both embedded fonts are fine, but the BASKVILL.TTF font is not used as far as I can see or expect.
I don't get this at all. The font that you refer to is embedded in the PDF. You have to actually set that for for it to use. Of course the font needs to be available.
Seems that it also works without a specified font 🙂
I wouldn't recommend 'fixing' VI lib VI's.
I agree that replacing files in vi.lib is a last resort and normally a no-go. I didn't place full trust in this library over Labview upgrades but so far it has always remained stable since LV6, so my distrust is no longer valid. When replacing files in vi.lib is done, make sure you document this very well in your own procedures and also make sure normal function is not broken. This is the reason why I only changed the error text and not the error dialog popping up. (thinking of it.. I will add this change to the idea's exchange, a better place then here)
My typical way of working, if needing to change vi.lib files, is to copy the vi.lib file to my own library, modifiy it there and no longer use the vi.lib file (or better if possible, make a wrapper around the vi.lib file). In this case I do not use the vi.lib 'read characters from file' in vi.lib but made my own clone that has error handling as normal.
kind regards,
Mark
Idea exchange added: https://forums.ni.com/t5/LabVIEW-Idea-Exchange/Include-filename-in-error-code-for-file-handling-func...
@beuvink wrote:
Hi Wiebe,
thanks for the quick reply, as always 👍
I've changed the 'Open file+.vi'. I've added a format into string in the 'build error' case in the end.
The file throwing the error dialog is 'read characters from file.vi' in the same llb. (vi.lib\Utility\file.llb). See screenshot below.
I am using the set font vi in a slightly different way. Instead of custom1 I select any of the default fonts in the Font ID enum. I do not connect the font file input (as font file availability is not stable over systems).
When the file is missing, pdf is generated fine, using the Helvetica font embedded. (acrobat->file properties). The first font fails:
If the system contains BASKVILL.TTF both embedded fonts are fine, but the BASKVILL.TTF font is not used as far as I can see or expect.
I don't get this at all. The font that you refer to is embedded in the PDF. You have to actually set that for for it to use. Of course the font needs to be available.Seems that it also works without a specified font 🙂
Don't use PDF Set Custom Font, use PDF Set Standard Font!
PDF Set Standard Font switches fonts to one of the standard fonts, the entire reason for existence of PDF Set Custom Fonts to add a font.
And yes, documentation could be better.
