The unexpected complications of minor features

You're viewing a single comment in a conversation. View all the comments
  • 4 Comments

  • Order by
  • I remember suggesting to add the minor suggestions section! I thought it had been taken very literally though, where a minor suggestion must take maybe 5 minutes or less to implement otherwise it will be treated like a regular suggestion.

    I made a minor suggestion I had posted months ago:

    It was to tweak the bookmark window for event sheets - to add some more bookmark colours and add tabs on the bookmark window to group. I explained many benefits to this suggestion, and included further ideas to expand on the suggestion but I only did this as little extras haha.

    • So, my logic was thinking this would be very easy to do, maybe 1-2 hours, just copy paste the bookmark image icon and change the hue, make sure c2 projects would default to the "red" bookmark when imported, add some tabs into the window or even a drop down window if it was easier (could be recycled from elsewhere in c3).

      May I ask, what was the tricky part for this idea? Just to educate me so I don't underestimate in future!

        • [-] [+]
        • 2
        • Ashley's avatar
        • Ashley
        • Construct Team Founder
        • 2 points
        • (1 child)

        User interface is actually extremely complicated and time consuming to design and implement. This is a classic example of thinking it's quick and easy but it's actually one of the harder things to do. UI looks easy but it takes a very great deal of work to make it "just work" that well, so in general any idea that involves any change to the UI is not a minor suggestion.