How to report bugs


#1

Subform has some rough edges, and we need your help grinding them smooth.

When you run into a bug in Subform, help us fix it by following these steps:

  1. Check to see if the bug has already been reported.
    • If it has, please add any comments to the existing topic rather than creating a new one.
    • If it hasn't, please create a new topic in this category ("bugs").
  2. Create a short, descriptive title. (Bad: "Components broken". Good: "Style change to component instance doesn't update other instances")

  3. Say what version of Subform + Operation System you are on ("I'm using Subform 893851e on OS X version 10.9.5")

  4. Explain what happened, and how it's different from what you expected to happen. ("I expected the background color change to occur in both instances of my component, but it only occurred in the one I was directly editing. The second component instance didn't change.)

  5. Include steps to reproduce the bug in a new document.

The faster I can reproduce the bug, the faster I'll be able to fix it.
Here's an example of good reproduction steps:

  • Select a blank artboard and press "enter" to create a new box.
  • Click the box to select it.
  • Press "enter" twice to add two children.
  • Convert the box to component by pressing "command-k".
  • Duplicate the component instance by pressing "command-d".
  • In the tree, under the first component instance, drag the second child into first.

What is SUPER HELPFUL is a screen recording showing the bug from a blank, new document.

On OS X, you can create screen recordings using the built-in Quick Time Player.
You can share the recording via a Dropbox link or private YouTube URL.

Thanks!

Kevin


#2

#3