We do launch xvkbd on clicking the virtual keyboard button. Is it not launching for you? We also show an error message if we couldn't launch it?
This functionality was missing in a few places (changing combination of an existing safe, setting up a new safe, opening an existing safe from File menu). I have added it (in the trunk). Should be available in the next release.
But in all other places, it should work for you.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2010-12-14
My points was that xvkbd is not a dependency to install passwordsafe and I thought that it was a bug, but it's true that is not indispensable.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We do launch xvkbd on clicking the virtual keyboard button. Is it not launching for you? We also show an error message if we couldn't launch it?
This functionality was missing in a few places (changing combination of an existing safe, setting up a new safe, opening an existing safe from File menu). I have added it (in the trunk). Should be available in the next release.
But in all other places, it should work for you.
My points was that xvkbd is not a dependency to install passwordsafe and I thought that it was a bug, but it's true that is not indispensable.
Rony - what do you want to do about this?
I would rather not add a dependency, because xvkbd depends on a lot of other libs. Who knows what is installed by default on each platform.
But we can add it as a "recommended" dependency, I guess.
I think that adding xvkbd as a "recommend" dependency is a good idea.
Additional dependency was added to cmake configuration with commit [d0b439].
Check for virtual keyboard (xvkbd) was added with commit [77325b].
Released with 1.06BETA