[PD-dev] [ pure-data-Feature Requests-1907998 ] give clues that object's constructor has failed

[SourceForge.net]

Feature Requests item #1907998, was opened at 2008-03-05 14:36
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=478073&aid=1907998&group_id=55736

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: puredata
Group: None
Status: Open
Priority: 5
Private: No
Submitted By: IOhannes m zmölnig (zmoelnig)
Assigned to: Miller Puckette (millerpuckette)
Summary: give clues that object's constructor has failed

Initial Comment:
currently, when an object (that is: non-abstraction external) fails to create, this can be of 2 reasons:
- the objectclass is unknown (and cannot be found on the filesystem)
OR
- the objectclass is there, but the constructor has failed

both look the very same in the patch (a dashed box)

however, it would be nice if these could be distinguished on a patch-level, so the user have a clue what actually happened (without having to read pages of pd-console output)

i would suggest using a different colour for the two cases (e.g. grey out a known object that fails to construct)

additionally it would be nice to be able to access the right-click help of an objectclass if it failed to construct. (so people can get an idea what they did wrong)


it shouldn't be too hard to do, as Pd already has a notion of what happened.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=478073&aid=1907998&group_id=55736