Loading ...
Sorry, an error occurred while loading the content.

23334RE: [Clip] Re: Clips self destruct

Expand Messages
  • John Shotsky
    Oct 30, 2012
    • 0 Attachment
      I am not saying you should not be able to run a clip on itself. I'm saying it should not be possible for NT to
      AUTOMATICALLY open the clip tab and then run the library on it. The reason it opens it is because it is the only tab
      left, having closed each previous file (and tab) due to not finding a file it was looking for. (I'm not sure why it
      closes those files either � it should just give the error and then stop, since the user cancels.) The clip tab certainly
      is not the missing file either, so it should do the same thing it does for all the other documents. I would much rather
      see the clip tab closed than destroy my clip library.

      RecipeTools Web Site: <http://recipetools.gotdns.com/> http://recipetools.gotdns.com/

      From: ntb-clips@yahoogroups.com [mailto:ntb-clips@yahoogroups.com] On Behalf Of flo.gehrke
      Sent: Tuesday, October 30, 2012 05:20
      To: ntb-clips@yahoogroups.com
      Subject: [Clip] Re: Clips self destruct

      --- In ntb-clips@yahoogroups.com <mailto:ntb-clips%40yahoogroups.com> , "John Shotsky" <jshotsky@...> wrote:
      > Obviously, (a clip) should never run on itself, and you can't force
      > to run on itself if you try, but it DOES run on the clip
      > library if it loses its place,...

      If it has been started from a clipbar, a clip could absolutely run on itself.

      I use that method in order to search & replace in a clip opened in the clip editor. Also, I've got a clip that writes a
      selection of most frequently used commands and functions into other clips or even into itself.


      [Non-text portions of this message have been removed]
    • Show all 12 messages in this topic