Wink‎ > ‎

Known issues in Wink 2.0

This is a list of known issues in v2.0. The latest version is Wink 2.0 build 1060
This list will be updated by the moderator/webmaster so if you find new issues open a new thread and discuss about it (and if it is really a bug it will be added here). Also please check two other posts with Frequently Asked Questions and How to's / Tips & Tricks as these might contain the answers to your questions. 

Open Bugs. 

1. PDF files exported from Wink can't be printed on Windows
A bug in the exported PDF files does that they can't be printed normally. A workaround that has worked for some is to "print" the PDF file to a new PDF file through a PDF Printer Driver like Adobe Distiller. 

2. Gap between frames in thumbnail list
When having a large number of frames (>500) in a project you might see a gap somewhere in the list of thumbnails. This is just a visual bug and doesn't affect the project or rendered presentation. 

3. Text files exported from v1.5 can't be imported in v2.0
Exported text files from Wink 1.5 reports 1 textbox/callout used in all frames even when there are none. Version 2.0 expects it to say 0 textboxes/callouts in this situation and therefore won't import the text file at all. The workaround is to either manually fix the text files before importing in v2.0 or import them back into v1.5, save the project and open the project in v2.0. 

4. Hotkeys doesn't work under Linux when NumLock is switched on
If the NumLock key is switched on, hotkeys in Wink do not work under Linux. So make sure to turn off the NumLock key while capturing. 

5. Capturing doesn't work under Linux when a menu is open
The capture hotkeys may not work when a menu is open in any application because the window manager takes control of the keyboard and wink does not receive the events. As a workaround you can start timed capture just before opening the menu and keep it capturing shots as you open the menu and click on the menu item, then stop timed capture. 

6. Wink won't run on Ubuntu 6.06 with Chinese language
The linux version of Wink works correct with Ubuntu 6.06 and language set to english (or danish) but not when language is set to chinese. This can be tested with the Ubuntu live/desktop cd where language can be set when booting. 

7. Browsing files in Wink doesn't work with Japanese language
When Wink is set to Japanese language you can't see any files in the Browse dialog while for instance adding a background. A possibly derived bug is that when typing the image file name in the Background browse dialog and then pressing Enter Wink adds a ')' to the end of the file name. This can be reproduced on non-Japanese versions of Windows, you just have to set every language option (except keyboard) to Japanese in advance. Interestingly this issue doesn't appear with Wink (and Windows) set to Chinese language. 

8. Rendering very large projects can crash Wink
Rendering or doing other intensive operations like resizing all frames can crash Wink when the projects are very large. This is projects with around 2000 frames or more and the frame dimensions being 1024*768 or larger. It seems to happen when Winks memory usage reaches the available amount of (physical?) memory. 

9. Input-driven capture doesn't work with IE7 in Vista and Command Prompt
Input-driven capture does not work with Internet Explorer 7 in Vista (haven't tested with IE7 in XP) and also not with Command Prompts in any version of Windows. Neither mouse or keyboard actions are captured. 

10. Input-driven capture doesn't work with Windows 7 64 bit.

As a work around, there is an AutoHotkey script attached to the post!topic/wink-discuss/7kujYMIyVZw that can be used.

Issues that will not be fixed and those not directly related to Wink 

1. Rendered presentations hangs/freezes when played and/or parts of control bar and buttons doesn't display
Flash files only works correct when they have no more than 16,000 rendered frames. When this limit is exceeded the presentation freezes (but audio might continue playing) when reaching frame 16,000 and other issues might also appear. The default output frame rate of 20 fps means a presentation must max. be 800 sec. = 13.3 min. long to work correct. The workaround is to lower the output frame rate, trim the project or split the project into multiple projects. 

3. URL buttons doesn't work when playing flash file locally on computer.
By default version 8 of the Flash Player does not allow opening external sites from a locally played flash file. This security setting can be changed at the following website: 

4. Custom Windows XP Themes might hide Wink Controls.
If you are using a non-default Windows XP Theme some controls in Wink's user interface might either show up as black areas or be completely hidden. This is a bug in the custom theme being used so check if the author of the theme has released a new version. 

5. Buttons in PDF files goes to wrong page/frame
When using Continuous view in Adobe Reader all buttons in a PDF file exported from Wink will go to the page/frame after the actual frame they should go to. The buttons work correct when Adobe Reader is setup to the default Single Page view. This is an issue with Adobe Reader and not Wink and hopefully will be corrected in future releases of Adobe Reader. 

6. Flash output sometimes looks garbled with palette 
This is due to a bug with the Flash player. You can either render the flash output without a palette, or create another palette with a different number of colours to work around this bug. 

7. Wink closes/exits when activating input-driven capture
Some anti-spyware tools might see Wink as a keylogger when input-driven capture is used because Wink will react (capture screenshots) when keys are pressed in this mode. The program "PCTools Spyware Doctor" will for instance close Wink when input-driven capture is activated. To avoid this tell the anti-spyware program to ignore Wink. And just for the record Wink doesn't contain record anything except the actual screenshots for your projects and doesn't contain any spyware-related tools.

8. Increased memory usage with Flash Player 9 compared to v8
The memory usage while playing a Wink presentation in Flash Player 9 is very different from playing it in version 8. In version 8 the used memory is flushed every other second or so, which keeps the memory usage very low. In version 9 of the Flash Player the memory usage rises continually until the presentation has finished playing and can get very high when NOT using a palette to reduce the number of colors. Wink has no control over the flash player memory usage and the techniques which worked with player 8 are no longer working in player 9. 

9. UNC/network paths are not handled correctly
If Wink is installed on a network and the user tries to start it directly from the network drive, Wink won't start but instead show error messages like "XRC resource 'midContextMenus' (class 'wxMenuBar') not found!". A simple workaround is to map the network to a drive letter and then execute it through the drive path instead. 
This will not be fixed due to an implementation difficulty, please use the above workaround instead.