Here you will find answers to Frequently Asked Questions about Wink. Also please check two other posts with How to's / Tips & Tricks and known issues in the current version of Wink as these might contain the answers to your questions.
1. Why does the presentation look fuzzy/blurry when viewed in a browser?
This happens if you link directly to the swf flash file from your webpage as the browser will then resize the presentation to the viewing area. Wink generates an htm(l) file (specifying among other things the correct dimensions of the presentation) together with the swf flash file while rendering. You have to upload both to your website and link to the htm file instead of the swf file.
2. Why are the dimensions of the Wink flash file so small when imported into other programs?
Wink uses a novel compression technique to reduce the size of the default flash file. Unfortunately this means other programs normally can't import/convert it correctly (some programs do have the option to resize swf files). With version 2.0 of Wink you now have the option to render to a Uncompressed Flash file instead through the Project Settings. This file is larger than the default output format and therefore not recommend for normal use but it can be imported correctly into other programs.
3. Why is the audio quality reduced in the rendered presentation compared to how it sounds inside Wink?
The was done on purpose to get a reasonable compromise between audio quality and file size. The next release of Wink will add settings to control the audio quality in the rendered presentation.
4. Why does the cursor sometimes move before the screen is updated in the rendered presentation?
Each time this happens it is because a frame/screenshot is missing in the project likely because it wasn't captured in the first place with manual or input-driven capture.
If you are capturing manually by pressing the Pause key you have to capture a screenshot before and after each mouse action/click and the "after capture" must first be done when the screen is completely updated (e.g. web page has loaded) and before moving the mouse. This will lead to a correct rendered result.
If you use the automatic input-driven capture the rendered result is normally correct. But in situations where the actions are delayed on screen from the actual mouse click (like loading of "slow" web pages) you will see the same wrong behaviour in the rendered presentation. In this case you currently also have to do a manual screenshot with the pause key after the screen has updated and before moving the mouse. In future versions of Wink this capture mode will likely be improved.
When you already have a project with this problem you can solve it by a little editing. Let's say you have frame 1 and frame 2 and the problem is that the cursor moves to a position in Frame 2 before Frame 2 is displayed. To fix the issue you must copy frame 2 and paste it as a new frame (1.5) between the original frame 1 and 2. Afterwards you must copy the cursor object from frame 1 and paste it into the new frame 1.5. These two copy-paste actions fixes the rendered result as the new intermediate frame contains the cursor start position that was missed previously.
5. Why is the size of the rendered swf file often larger after resizing all frames to smaller dimensions in Wink?
When you downsize a project, the crispness/sharpness of the images go away and it becomes a little fuzzy. Wink compression is tailored towards screen captured images so when the images are no longer crisp and clear as they are on the screen, the compression does not perform well. If you know beforehand what resolution you want the output to be, the best method is to capture only that area (not a large area and downsize it).