Here are a bunch of bug reports that I found over the past month or so but haven’t posted yet. I’ve tested most of these to make sure they still happen on the current alpha editor (1.0.13); however, some may be outdated, since I first wrote them down after using versions 1.0.10 through 1.0.12. I’ve tried to eliminate ones that I know have already been seen or fixed.
Anyway, hope this is useful! 
Major Bugs
-
Sometimes download of .wick fails on Firefox. Sometimes I save a file then refresh, not noticing the download has failed, then later my only option is to restore from an out-of-date autosave. Can Wick detect this and warn you?
- Downloads haven’t failed lately. Maybe this has been fixed
- Downloads haven’t failed lately. Maybe this has been fixed
-
If a clone causes an error, it is not completely deleted when the project stops running. In this example file, a clone that was generated at runtime is still selected when the project stops. BugReport_PlayError.wick (434.1 KB) (Go to frame 2 and play. Click on a letter button to cause the error.)
-
Clear
setInterval()loops (as well assetTimeout()) when done testing. (This might be fixed already, I’m not sure)
(https://psychogoldfish.newgrounds.com/news/post/1054092) -
Clip position differs between code and inspector. The inspector seems to tell you the top-left of the bounding box, but code gives you the location of the registration point. BugReport_PositionAintRight.wick (1.4 KB)
-
BugReport_GotoOrderOfOps.wick (1.5 KB)
Say you have a Clip with two frames, each containing a text object, and it is currently stopped on frame 1. Running this code would not work:Clip.stop(); Clip.gotoAndStop(2); Clip.text.setText("Hi!");-
gotoAndStop(2)apparently does not run until the next frame or the end of this frame, soClip.textfrom frame 1 would get set first. But then the frame changes to show a different text object, so the message doesn’t appear to change. (I’ve reported a similar issue here.)
-
-
gotoAndStop()andgotoAndPlay()can be used with out-of-range frames.gotoAndStop()is especially dangerous in this regard, because if you put the root timeline to a frame that doesn’t exist, it effectively freezes the project with a blank screen. -
In an older version (.12, maybe?), I ran into a bug that caused one of my Clip’s frames to be deleted. I can’t reproduce it, though. I have a vague idea of what I did:
- Extend frame a lot
- Click underneath the layer in the blank space
- Huh? Frame disappears, replaced by a blank frame 2
- Maybe it has to be inside a Clip.
- I also usually kept my browser zoom at 80% or 90%, resulting in a slightly glitchy-looking timeline (see below).
-
Undoing a script edit while the script editor is closed silently deletes your work! To make this happen, type something in a script, close the script editor, select another object (to trick the undo system), and then hit Ctrl-Z multiple times. Bring the script back up and your new code will be gone.
- Instead, pressing Ctrl-Z after closing the script editor should bring it back up and select the last code you changed. Press it again to undo this code.
Minor Bugs
-
Dynamic text wraps differently from static text and has different line spacing
- In general, graphical issues like this probably won’t happen in the next version since pixi.js was removed, but I wanted to report this anyway.
-
Changing browser zoom while editor is running sometimes causes paths/Clips to render at the wrong size and position during play mode. (Usually too big, and offset to the bottom-right.) Refreshing fixes the issue while maintaining your chosen zoom level.
-
Trying to double click to exit a Clip while a locked layer is selected gives a “trying to edit locked layer” error.
-
“Ctrl+C” and “Ctrl+V” to Copy and Paste frames doesn’t always work. I find that I often have to click the stage and then click the timeline before it will work.
-
Text can be skewed by rotating it then scaling it (because the bounding box resets) but this doesn’t apply when running project
- The bounding box shouldn’t reset like that, but skewing objects is still a very useful feature and should be kept.
- The bounding box shouldn’t reset like that, but skewing objects is still a very useful feature and should be kept.
-
You can’t send a text object in front of or behind another text object.
-
Error tooltips spawn at wrong position. (My mouse is on the top red [x] icon.)
- If the scripting window is too close to the bottom-right, the tooltip will not be visible at all.
-
Pressing ` to toggle the script editor 3 times in a row fails the third time if an object or frame is selected. There is also some lag before it comes up.
-
Can’t manually type in shape opacity (example:
0.3), as the field removes all periods. If I type really fast and press enter, I can sneak it in, though, and it will work. -
In Flash, while editing a symbol, you double-click the background to exit. Wick has a similar behavior, except selecting one of the objects inside the Clip can count as one of the clicks. This means if you do either of the following, you will unintentionally exit the Clip.
- double-click a path
- click an object and then click the background shortly after
-
Maybe there should also be a very short grace period (like half a second) after you enter a click where “double-click to exit” doesn’t work. This prevents you from entering a Clip and accidentally exiting it immediately.
-
When tweening a clip, sometimes trying to select the Clip after selecting the timeline doesn’t work, even if the playhead is at a tween keyframe.
-
Tween keyframe highlights often stay in after you deselect it.
-
Brush cuts off when drawing a stroke that extends outside the visible area. Sometimes the area the brush will draw in gets misaligned with the view.
-
Right-hand side of Timeline is bugged if you start Wick with the browser is zoomed out (Firefox)
-
“Delete script” brings the script editor up in front of the Delete panel.
)
