XnView Software

This occurs in view mode (not sure about others): Open xnview, open an image, click the filters button. You will get an error instead of the filters menu: "this application has failed to start because RAPI.dll was not found, reinstalling the software may fix it". Once you close the error box, the filters menu appears to work properly (although the deinterlace filter is missing, and the menu gives the appearance of being truncated). The error appears once per session. What "application" is trying to start?? Also, a websearch on "RAPI.dll" indicates that it's something related to syncing with a portable computer, which makes me even more confused.

Confirmed. It's probably just an unneeded depency to RAPI.DLL

Confirmed. I had Batch rename dialog appear after this, even though I never selected it!

Hi All !

• Confirmed too ! I see it since yesterday…

- I tried to capture the message - strange, it has a red menu-bar here, that is abnormal -

• When I imported the Clipboard for that capture, I got only a white empty rectangle !

- It occured again here one hour ago, like Drahken points out at each new session,
as soon as I open the filter menu and I click a category…

KR
Claude
Clo

Drahken wrote:This occurs in view mode (not sure about others): Open xnview, open an image, click the filters button. You will get an error instead of the filters menu: "this application has failed to start because RAPI.dll was not found, reinstalling the software may fix it". Once you close the error box, the filters menu appears to work properly (although the deinterlace filter is missing, and the menu gives the appearance of being truncated). The error appears once per session. What "application" is trying to start?? Also, a websearch on "RAPI.dll" indicates that it's something related to syncing with a portable computer, which makes me even more confused.

It' not an error It's the PocketCE plugin, so please remove AddOn/Pocket.xnp

Removing that file does stop the error. It would be a good idea however to do something different about it in the final release. Either make it optional to install, or have it disable itself if it doesn't find the activesync files, or something. If publicly released as-is, the forum will be flooded with complaints about the error (especially since it reappears during every single session).

xnview wrote:It' not an error It's the PocketCE plugin, so please remove AddOn/Pocket.xnp

Yes that did do the trick.

Having such an error message in XnView is not acceptable. --> Confirmed.

helmut wrote:Having such an error message in XnView is not acceptable. --> Confirmed.

No, it's a plugin if you have all dll for pocket CE, so i can't check that...

xnview wrote:

helmut wrote:Having such an error message in XnView is not acceptable. --> Confirmed.

No, it's a plugin if you have all dll for pocket CE, so i can't check that...

There is a plug-in .\addon\Pocket.xnp which comes with XnView and causes an error message to be displayed.
From my point of view this is a problem in XnView which needs fixing. Either the plug-in must be removed or the bug fixed.

@Pierre: Please explain in more detail why this is not a bug.

helmut wrote:@Pierre: Please explain in more detail why this is not a bug.

This plugin will be not with xnview package, but external download. So user must download this plugin only if he has Pocket DLL

Doing it that way should be fine. If the plugin comes with xnview itself (as it does in the beta) then it would be a problem, but if it's something that has to be downloaded/installed seperately then people shouldn't get this error (unless they're morons ).

Drahken wrote:Doing it that way should be fine. If the plugin comes with xnview itself (as it does in the beta) then it would be a problem, but if it's something that has to be downloaded/installed seperately then people shouldn't get this error (unless they're morons ).

O.k., I understand. I wonder whether it should be excluded from the next testing package. Or is there anything to test with this plug-in (if so this should be tested explicitely by some people)?

helmut wrote:

Drahken wrote:Doing it that way should be fine. If the plugin comes with xnview itself (as it does in the beta) then it would be a problem, but if it's something that has to be downloaded/installed seperately then people shouldn't get this error (unless they're morons ).

O.k., I understand. I wonder whether it should be excluded from the next testing package. Or is there anything to test with this plug-in (if so this should be tested explicitely by some people)?

Yes, i'll remove it from next package...

So we can move this to Closed.