![]() ![]() I’d be mindful that not everyone uses with Tinderbox so asking Eastgate to track 's development and re-test each release might be more dev work than imagined. 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. ![]() In no docs, email 's dev any ask for detail Check some app’s documentation for what data is put into the drag.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).See what sort of note is made and if any KA are set.Try drag/drop or paste into Tinderbox view pane.Personally, my approach with first testing using data from with Tinderbox would be this: 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.ĪTbRef certainly reports support for known apps that have specific per-app support built-in (mainly found here). 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. My years of beta testing for a variety of apps would suggest otherwise. For instance, sometimes may not document what it puts on the clip board (or in a drag) or mis-declare its data type. 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 (assuming they are even willing) to check sending/receiving apps are doing things the same way. Heavy users of usually follow up with “Why doesn’t Tinderbox find all the things from that I assume it is providing?”. Stepping back, this is an unbounded question: “What from may get imported, and how do I know?”. … which brings me back to my original question: All the Scrivener-attributes are brought over – but not displayed as Key Attributes automatically … One can either drag them in or even open them as new TB-file. But once a Devonthink-file has more than 1 tag – none of them is assigned to $Tags anymore.But again: Not automatically displayed as Key Attribute. ![]()
0 Comments
Leave a Reply. |