Get answers to most commonly asked technical questions about WinPack. If you don’t find the answer here, please send us your question using the support forum and we will add it to this FAQ section after answering you.
No, it does not. It provides the wrapping only for the really useful features of the Windows platform that mostly are not available in Java.
Actually, there is no such "GetWindowText" function in the user32 library, but there are two appropriate "GetWindowTextA" and "GetWindowTextW" functions, representing ANSI and Unicode versions, respectively.
Yes, it is possible. There is a special Wnd class for this. Please view the WinPack Demo application that demonstrates such this ability.
Yes, it is possible. You can do this using the Wnd and Region classes from WinPack library. Please view the WinPack Demo application that demonstrates such this ability.
Under the Windows platform, the Function.invoke() method returns the value that is an error code. This error code can be translated to an appropriate error message by using the LastError.getMessage(long errorCode) method.
Yes, it is possible. WinPack provides a special WindowProc class which lets you substitute the standard window procedure of a Swing window and listen to its messages.
Yes. There is a special FileSystem class that provides such ability.
Yes, WinPack provides it. All MAPI related classes can be found in the com.jniwrapper.win32.mapi package.
Yes, in WinPack there is Processes API that allows you to manipulate processes, including process termination.
To terminate a process, you should use the Process.terminate(long exitCode) The close() method just closes the handle of a given process.
Yes, we have added such ability to WinPack version 3.0. There is a special ShellEventsSubscriber class (from the com.jniwrapper.win32.shell.events package) that provides API for this purpose.
Yes, WinPack provides special API for this purpose. You can find it in the com.jniwrapper.win32.winhttp package.
There is a special com.jniwrapper.win32.system.SystemVariables class that provides such ability.
The Services API from WinPack library (com.jniwrapper.win32.service package) provides such ability.
The number of receiving events depends on options of the FileSystemWatcher object. There are several kinds of notifications in the FileSystemWatcher.WatcherOptions class and they all set to true by default. That's why you get many FILE_MODIFIED events. But you can easily disable the unwanted ones. For example:
FileSystemWatcher watcher = new FileSystemWatcher(folder, true);
FileSystemWatcher.WatcherOptions options = watcher.getOptions();
options.setNotifyChangeAttributes(false);
options.setNotifyChangeSize(false);
and so on.