A place for design notes

Please follow the format below for requesting a feature.

The problem that this feature will solve:

To keep working in the program and not have to leave it to create design notes, or instructions for next time I’m in the app.

Brief description of the outcomes that you expect from this feature:

A reminder to complete something, a checklist of items left to do, notes left of what I’ve completed. Can also be used if you bring in collaboration features.

What can’t you achieve without this feature?

I have to leave the app and create notes elsewhere and not where I need them, in the app.

Thanks.

15 Likes

I second this. Would love to be able to add comments to design parts, objects, etc.

3 Likes

+1 also.
I would love to have:

  • notes attached to sketches so I can keep a trace of how the sketch and the constraints are built, so I have a chance to remember it later on
  • notes attached to history’s step so it’s easier later on when I comeback to modify the design.
3 Likes

I would also appreciate to add comments or quick note to parts I designed.
Suggestion: This could be made \ managed in the measurement Window…?

3 Likes

I would find this useful

2 Likes

I often come hback to designs months later - I have notes every where but to have them inside Shapr would be so more efficient

I would also like this however… I’m going to point at the Operating System designers (Apple, Microsoft, Ubuntu or whatever) for not supporting better cross application integration support.

For example, in the Apple world, being able to smartly link a sketch to a Goodnotes page should be possible. I can’t expect Shapr3d to build something like Goodnotes into Shapr3d. Nor would I expect Goodnotes to be aware of Shapr3d sketches. What I can hope for is for the Operating System to provide an API that allows this level of integration with security in mind. Basically allow links from one app to either where both apps are actually blind to each other. If this API existed, each app developer wouldn’t have to roll their own or integrate to specific apps. All they would have to do is support linkable content on the source app. Then any destination app can be eligible to link to it. “mime”-like descriptions of the linked content (and even direct access to it) could be an optional part of that API to support more sophisticated integration.

This would drastically reduce the need for an app to roll sub-par support for certain features or app specific integration and let the user decide which app to use for that purpose.

I like the idea. Right now I add text on a construction plane next to the body.