Note that there are some explanatory texts on larger screens.

plurals
  1. USRob Glassey
    primarykey
    data
    text
    plurals
    1. This table or related slice is empty.
    1. COThat's good! If you see documents resurrecting in future, check you don't have an instance variable somewhere else that has an open copy of that same document. No matter how often you delete off disk, if there's a UIDocument instance hanging onto an open copy somewhere else in your app, auto-save is likely to resurrect it. You need to make sure that *instance* has it's copy of the file closed too. But IMHO threading and background stuff, while really cool when it works, can be a right pain in the ass to get working! There are so many gotchas to watch out for. It's worth it though.
      singulars
    2. COWhy do you set up a document before you delete it? That seems unnecessary. At a guess I would say you're deleting the file on disk, but UIDocument's autosave is kicking in and saving it again. Are you certain it's closed when you perform the delete? Also, it depends on how your query is set up, but stopping and starting the query while performing a delete seems unnecessary. Also stopQuery doesn't necessarily stop immediately (if you need this probably use disableUpdates instead) - from the docs for stopQuery: `The receiver first completes gathering any unprocessed results.`
      singulars
    3. COBeat me to it! Also, if you were using `description`, you weren't necessarily comparing like with like - this shouldn't really have caused an issue if the underlying object was a string, but description is normally used to get a debug printed version of an object, and it can be overridden, so won't always necessarily come out the same. It is a lazy way to convert an object to a string, ignores localisation issues etc - better to use a formatter, and then you avoid the possibility of having the functionality of `description` change unexpectedly on you down the road.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload