Length of Time to fire up the edit screen of VB component

Something that I noticed sometime back but did not mention is the length of time for the edit screen to come up first time around. It is OK after I do it once.

Not a serious issue but I always have to remember to do it right at the beginning if I think I will be requiring to use the VB component.

Regards

Replies to This Discussion

Permalink Reply by David Rutten on August 4, 2011 at 3:15pm

It should take longer the first time, that's when all the dlls need to be compiled that are required for showing the code editor. Are you saying that the longer you use Grasshopper, the longer the code editor start-up time is?

David Rutten

david@mcneel.com

Poprad, Slovakia

Permalink Reply by WT4 on August 4, 2011 at 4:04pm

No after I have fired it the first time around, any subsequent use of the edit screen is instantaneous and is not affected at all by how long my grasshopper session is.

Permalink Reply by David Rutten on August 4, 2011 at 6:42pm

Then I'm confused by this comment: "...I always have to remember to do it right at the beginning if I think I will be requiring to use the VB component."

If it takes the same amount of time to start the editor for the first time -no matter when you do this-, then why do you need to anticipate your usage 'at the beginning'?

David Rutten

david@mcneel.com

Poprad, Slovakia

Permalink Reply by WT4 on August 6, 2011 at 2:08am

It is when I am giving a lecture and I do not want to loose the flow of the lecture.

Regards

William

Permalink Reply by David Rutten on August 6, 2011 at 4:34am

Ahhh! It all makes sense now. Well, then yes, doing it at the beginning is the only way to get rid of the delay later on. The delay shouldn't be more than 2~4 seconds or so though, it's a little over 2 on my machine.

This is the way .NET works. All .NET dlls are a binary version of the source code, they are not really compiled in the common sense of the word. When you make a dll, the VB or C# or F# or C++/CLI code gets translated into a language called MsIL, which stands for Microsoft Intermediate Language, .NET dlls are half-baked. This is why it doesn't really matter what language you develop on, it all gets 'compiled' to the same stuff.

Then once the dll (or exe or whatever) runs, every function is really compiled into machine code the first time it is run. This is why things always take a little bit longer the first time they run. When the VB/C# code editor pops up a lot of code needs to be compiled.

David Rutten

david@mcneel.com

Poprad, Slovakia

RSS