…I heard my name.
Stepping back, this is an unbounded question: “What from [some app] may get imported, and how do I know?”. Heavy users of [some app] usually follow up with “Why doesn’t Tinderbox find all the things from [some app] that I assume it is providing?”. The reality is less simple.
Those who read the release notes in detail will know some of this integration isn’t simply a case of Tinderbox dropping the ball but requires Eastgate to work with the authors of [some app] (assuming they are even willing) to check sending/receiving apps are doing things the same way. For instance, sometimes [some app] may not document what it puts on the clip board (or in a drag) or mis-declare its data type. As users, we assume this ‘just’ works. My years of beta testing for a variety of apps would suggest otherwise.
This is all a polite roundabout way of saying - are we asking the right question here? The expectation I parse from posts above is an assumption Tinderbox should put all ‘extra’ information, for which it has a suitable (how to tell?) attributes, as KAs. When the unexpected happens, experience shows users blame the receiving app (or the one they use less often/know less well) which isn’t exactly logical.
aTbRef certainly reports support for known apps that have specific per-app support built-in (mainly found here).
Personally, my approach with first testing using data from [some app] with Tinderbox would be this:
- Try drag/drop or paste into Tinderbox view pane.
- See what sort of note is made and if any KA are set.
- If I suspect other data might/should be there, I’d open Get Info, tear off the pop-over, resize to show more data then select the attributes panel and cycle through the attribute groups to see what’s there - any item in bold is non-default).
- Check some app’s documentation for what data is put into the drag. In no docs, email [some apps]'s dev any ask for detail
- With clear detail of what’s in the drag and what doesn’t show up, drop an email to Tinderbox support asking if the omission is by design or if it could be supported. I’d be mindful that not everyone uses [some app] with Tinderbox so asking Eastgate to track [some app]'s development and re-test each release might be more dev work than imagined.