npQrco plugin

About this plugin

This plugin allows you to generate QR Codes (PNG and Bitmaps images) from your publications, specifiying various options like the image dot size, margin, background and foreground colors, error correction level, etc.

The plugin allows you to generate QR codes from plain text and of course can use this text to format the appropiate information to generate special QR Codes for emails, SMS, VCard, geolocation points, etc.

Thirparty

This plugin are imposible without the aid of this people:

Thanks a lot!

npQrcoGenerateBmp

Generate a QR Code and save it into the specified BMP image file. The result variable store "True" if everything is OK, or "False" if an error occur. In this last case the [LastError] variable store information about the error.

↑↑

npQrcoGeneratePng

Generate a QR Code and save it into the specified PNG image file. The result variable store "True" if everything is OK, or "False" if an error occur. In this last case the [LastError] variable store information about the error.

↑↑

QR Codes formats

QR Codes are composed by plain text, however, you can incorporate certain text formats in order to prepare special QR Codes which point to URL's, email addresses, SMS's, VCard's, etc. Currently are not an standard to follow, but you can take a look at this article from the ZXING project, which provide useful information in order to use this kind of special QR Codes.

↑↑

Included "quricol.dll"

For the correct use of this plugin you need to deploy your publication with the included "quricol.dll" file. You can found this file into the plugin installation directory and in the plugin samples directory. You need to copy this DLL in the same directory than your publication executable or in the Windows or System32 directory if you prefer.

↑↑

Action errors subroutine

All the NeoPlugins deal with errors in the same way that NeoBook does: when the plugin found an action error the [LastError] variable store information about the error, so you can take care about this variable when execute an action.

But all the NeoPlugins also incorporate an advanced way to deal with possible action errors. You can define a subroutine named OnNeoPluginActionError in order to be executed when some action error are found and you can use this variables inside:

[LastError] The last action error message.
[PluginName] Store the plugin name which cause the error.

Note that this error handling subroutine are shared for all the NeoPlugins, so you no need to specify a subroutine for every plugin you use in your publication because the same subroutine are recognized and automagically used by every NeoPlugin. Below you can view a sample of this subroutine code:

:OnNeoPluginActionError
  AlertBox "NeoPlugin Error" "Error [LastError] in plugin: [PluginName]"
Return

Also note that the use of this NeoPlugins error handling subroutine is completelly optional. You can continue using the [LastError] variable as usual and even use the both methods at the same time.