Hi Alan, ... Yes, that is what I have, just the 4 lines of code followed by nearly 10,000 lines of text to paste into a new document. I m working on a book &Message 1 of 3 , Mar 1, 2002View SourceHi Alan,
--- In ntb-clips@y..., "Alan C." <acummings@s...> wrote:
> If I have it right then what you have is a really large,
> long clipping of text that's in a clip and if no commands
> were in the clip then when > launched, this clip would
> merely paste its contents into the current doc
Yes, that is what I have, just the 4 lines of code followed
by nearly 10,000 lines of text to paste into a new document.
I'm working on a book & the 10,000 lines are generally
diagrams that I have created through various clips that
I've written. It's beneficial to keep all that text in
a clip because I can easily move the one .clp file
between the 3 PC's I general use.
I'm sure your solutions will work... I was just hoping
to get around splitting it into a file. But working
with your idea, I took only the text and moved that
into a new clip. My new clip looks like this:
H="test for empty doc1"
^!If ^$GetLineCount$ < 1 SameDoc
^!ToolBar New Document
Now it pops open immediately. I'll just write a little
clip wizard over the top of it so I can select the file
I want to open.
Thanks for the help!
Hi Mike, ... It sounds like it pastes immediately too? A called clip, that s kin to a sub routine. You ve made it more modular than it was before. Now all ofMessage 1 of 3 , Mar 1, 2002View SourceHi Mike,
>^!FocusDocIt sounds like it pastes immediately too?
>Now it pops open immediately. I'll just write a little
>clip wizard over the top of it so I can select the file
>I want to open.
A called clip, that's kin to a sub routine. You've made it more modular
than it was before.
Now all of this makes me wonder about NoteTab's parsing. From your report,
it appears to me that a called clip is not parsed until the (entire clip or
parent) clip has already begun to run and the called clip is checked/parsed
when reaches that particular point of the clips run. (might not be though)
That would explain the difference in behavior.
In my clip writing, I have been moving more and more to the use of called
clips. I liken them to sub routines myself. When clip written that way
makes it more modular. only 1 maybe 2 tasks per each called clip and/or
per each section in any clip keeps greater organization along with more
ease to look at it and translate to me what the clip does at each of its
excess on anything not good though. Balance. I wouldn't too too many
called clips makes it too hard for me to follow when writing,
plugin the term in some circles. more modular so that can add a plugin(s)
for more task(s)
Great! Thanks for sharing that. I learned something. Regards. Alan.