Detect pdf reader plugin

At this point in time, it is unknown whether the plugin is installed or not. Only certain plugins on certain browsers and platforms require NOTF. This method will call an event handler after plugin detection has fully completed. The handler can call the isMinVersion and getVersion methods to obtain the final plugin detection results.

Returns -1 if not installed or not enabled or is not the default viewer. Returns -3 if you supplied a bad input argument to the isMinVersion method. You are free to use the getVersion and isMinVersion methods inside event handler f. Returns 1 if plugin detection is done OTF and handler f has been called. It does NOT necessarily mean that the plugin is enabled.

By default, the returned version string is comma delimited and has the format of "A,B,C,D". If you wish to change the getVersion delimiter, then use: PluginDetect.

For example, PluginDetect. D" PluginDetect. It is possible that the browser may have other PDF viewer s installed, and that the browser will simply use one of those other viewers instead of Adobe's. Trying to detect when the Adobe plugin is the default PDF viewer across all browsers, all platforms, and all possible configurations is impractical at best.

There are too many problems in trying to detect this. Returns 0. Only certain plugins on certain browsers and platforms require NOTF. This method will call an event handler after plugin detection has fully completed. The handler can call the isMinVersion , getVersion and getInfo methods to obtain the final plugin detection results. The plugin version cannot be detected. Apparently the ActiveX control is not needed in this case. At this point in time, it is unknown whether the plugin is installed or not.

There are several possible reasons for this detection result: 1 The Adobe Reader software is not installed on your computer. However, the user can still download PDF docs and view them in the Adobe Reader standalone application.

In this case, the Adobe plugin is disabled and will not display any PDF docs within the browser. It is not possible to detect the plugin either. But the standalone app itself naturally can still display PDF docs. Returns -3 if you supplied a bad input argument to the isMinVersion method. You are free to use the getVersion and isMinVersion methods inside event handler f. Returns 1 if plugin detection is done OTF and handler f has been called. Returns 0 if plugin detection is not done yet NOTF and handler f has not been called yet.

The reason is that there are multiple vendors for PDF readers, and they use different version numbers. Also, a plugin version is irrelevant when the browser has built-in PDF support and thus requires no plugin. The plugin version is unknown. Returns At this point in time, it is unknown whether a PDF Reader plugin is installed or not. Only certain plugins on certain browsers and platforms require NOTF. This method will call an event handler after plugin detection has fully completed.

The handler can call the isMinVersion , getVersion and getInfo methods to obtain the final plugin detection results. But we have no way of knowing that since no attempt was made to detect any non-Adobe PDF plugins. You are free to use the getVersion , isMinVersion and getInfo methods inside event handler f. Returns 1 if plugin detection is done OTF and handler f has been executed. Returns 0 if plugin detection is not done yet NOTF and handler f has not been called yet.

Handler f will be called after detection has been completed. Returns -1 if error plugin name input argument not specified correctly.

This will cause the plugin to start up and run, assuming it is installed. Sometimes during detection, it may be necessary for PluginDetect to instantiate or attempt to instantiate the plugin.

Should this attempt be neccessary, the event handler f will run first, and then the plugin will attempt to instantiate. If it is not installed or not enabled, then it will not instantiate. Either way, the handler f will run before the attempt is made.