Getting started, prety stuck.

I think I figured out the Readonly bit (3) and (4). Not sure if I'm doing it right, but it seems to work. I was very confused by the layer/layers singular/plural mismatch:

Dim layer As SpanIndicatorLayer = Document.SpanIndicatorLayers(SpanIndicatorLayer.ReadOnlyKey)

SpanIndicatorLayers returns a SpanIndicatorLayerCollection yet it is assigned to a single SpanIndicatorLayer. I don't know why it works, but it works.

Basically I'm left trying to figure out why it's crashing when I call 

CodeEditor.Document.Language.FormatDocument(CodeEditor.Document)

with a NotImplementedException:

System::Windows::Forms::Application::ThreadException event occured
SENDER: System.Threading.Thread
EXCEPTION: System.NotImplementedException
MESSAGE: The language 'VB' needs to implement the 'FormatTextRange' method so that it can support code formatting.
SOURCE: ActiproSoftware.SyntaxEditor.WinForms
CALL STACK
at ActiproSoftware.SyntaxEditor.SyntaxLanguage.FormatTextRange(Document document, TextRange textRange)
at ActiproSoftware.SyntaxEditor.SyntaxLanguage.FormatDocument(Document document)
at Grasshopper.GUI.Script.GH_ScriptEditor.SetSourceCode(GH_EditorCodeLines lines) in C:\dev\Grasshopper\1.0\root\src\GH_ScriptEditor.vb:line 357
at ScriptComponents.Component_GenericScript.ShowScriptEditor() in C:\dev\Grasshopper\1.0\root\src\Components\ScriptComponents\Component_GenericScript2.vb:line 784
at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) 

Does that mean I'm not using the .NET languages add-on correctly?

--

David

Hi David,

1/2)  For these, make sure you read through the "Key Steps for Getting Started" items in the .NET Languages Add-on's "Overview" documentation topic.  That tells you how to get up and running with it and have automated IntelliPrompt working.  If you miss any of those steps, then it won't work properly.  You also can look at the source of our DotNetReflection demo since that shows an example of everything, including adding references to assemblies.  The .NET Languages Add-on language classes are CSharpSyntaxLanguage and VBSyntaxLanguage.  If you are using those then you are using the add-on.

3)  As you saw, our editor only tracks read-only ranges, not read-only lines.  You'd need to somehow convert your line data to the proper offset data so that you can make read-only ranges.  And be sure that you combine the adjacent ranges wherever possible to make things most efficient.  Also note that our offsets track line terminators with a single \n character.  So account for that when calculating offsets.

4) You could do it that way.  Or get the entire text once and split it by line terminator.

As for the SpanIndicatorLayers, you are calling an indexer there, which returns a single SpanIndicatorLayer item from a collection.

For the formatter, the exception message indicates that the VB language in the add-on doesn't implement a text formatter.  Languages can optionally implement one but that particular one doesn't at this time, thus the exception when you call that method.  You can add one on if you wish though as described in the "Code Formatting" documentation topic if you have your own logic for formatting (or find one on the web) that you'd like to apply.

For the formatter, the exception message indicates that the VB language in the add-on doesn't implement a text formatter.

Ok, appearently a Text Formatter isn't what I think it is then. If I can get away without one that's fine.

I'm running into more problems as the old ones get solved, but I'll put those on a different thread.

Thanks,

David