ZELDA v1.0 released (Expression Language editor)

Windows > Third Party Plug-ins, Programs, and Skins

<< < (6/45) > >>

jherbert:
Forgot to mention that I receive the following error upon startup (long version):

When I click continue the app starts just fine.

---------------------------------------------------

Informationen über das Aufrufen von JIT-Debuggen
anstelle dieses Dialogfelds finden Sie am Ende dieser Meldung.

************** Ausnahmetext **************
System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
bei Zelda.ZeldaUI.resizeGridColumns()
bei Zelda.ZeldaUI.LoadState()
bei Zelda.ZeldaUI.ZeldaUI_Load(Object sender, EventArgs e)
bei System.Windows.Forms.Form.OnLoad(EventArgs e)
bei System.Windows.Forms.Form.OnCreateControl()
bei System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
bei System.Windows.Forms.Control.CreateControl()
bei System.Windows.Forms.Control.WmShowWindow(Message& m)
bei System.Windows.Forms.Control.WndProc(Message& m)
bei System.Windows.Forms.ScrollableControl.WndProc(Message& m)
bei System.Windows.Forms.Form.WmShowWindow(Message& m)
bei System.Windows.Forms.Form.WndProc(Message& m)
bei System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
bei System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Geladene Assemblys **************
mscorlib
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4180.0 built by: NET48REL1LAST_B.
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll.
----------------------------------------
_Zelda
Assembly-Version: 1.0.0.0.
Win32-Version: 1.0.0.0.
CodeBase: file:///C:/Users/Joachim%20Herbert/Desktop/Zelda%201.0.2.exe.
----------------------------------------
System.Windows.Forms
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4084.0 built by: NET48REL1.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll.
----------------------------------------
System
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4084.0 built by: NET48REL1.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll.
----------------------------------------
System.Drawing
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4084.0 built by: NET48REL1.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll.
----------------------------------------
System.Data
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4084.0 built by: NET48REL1.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll.
----------------------------------------
System.Core
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4180.0 built by: NET48REL1LAST_B.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll.
----------------------------------------
System.Configuration
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4084.0 built by: NET48REL1.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll.
----------------------------------------
System.Xml
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4084.0 built by: NET48REL1.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll.
----------------------------------------
mscorlib.resources
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4084.0 built by: NET48REL1.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/mscorlib.resources/v4.0_4.0.0.0_de_b77a5c561934e089/mscorlib.resources.dll.
----------------------------------------
System.Windows.Forms.resources
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4084.0 built by: NET48REL1.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms.resources/v4.0_4.0.0.0_de_b77a5c561934e089/System.Windows.Forms.resources.dll.
----------------------------------------
System.Runtime.Serialization
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4180.0 built by: NET48REL1LAST_B.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Serialization/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Serialization.dll.
----------------------------------------
SMDiagnostics
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4180.0 built by: NET48REL1LAST_B.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/SMDiagnostics/v4.0_4.0.0.0__b77a5c561934e089/SMDiagnostics.dll.
----------------------------------------
System.ServiceModel.Internals
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4180.0 built by: NET48REL1LAST_B.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.ServiceModel.Internals/v4.0_4.0.0.0__31bf3856ad364e35/System.ServiceModel.Internals.dll.
----------------------------------------
System.RunTime.Serialization.resources
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4084.0 built by: NET48REL1.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Serialization.resources/v4.0_4.0.0.0_de_b77a5c561934e089/System.Runtime.Serialization.resources.dll.
----------------------------------------

************** JIT-Debuggen **************
Um das JIT-Debuggen (Just-In-Time) zu aktivieren, muss in der
Konfigurationsdatei der Anwendung oder des Computers
(machine.config) der jitDebugging-Wert im Abschnitt system.windows.forms festgelegt werden.
Die Anwendung muss mit aktiviertem Debuggen kompiliert werden.

Zum Beispiel:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

Wenn das JIT-Debuggen aktiviert ist, werden alle nicht behandelten
Ausnahmen an den JIT-Debugger gesendet, der auf dem
Computer registriert ist, und nicht in diesem Dialogfeld behandelt.

zybex:
Thanks for reporting JHerbert, fixed in v1.0.4.

Doof:
Awesome work. The only way it could be any better is if it were somehow directly built into MC. I haven't done any real work with it yet but as I was poking around everytime I thought "This is pretty nice, but I wish it did <this other thing>" followed shortly by "Oh! It DOES do <this other thing>!" Very well done.

Doof:
And just as I finish saying that I do find something that I, at least, would find useful.

Since I was previously using either VS Code or Notepad++ with the syntax highlighter to edit my expressions, I began saving them all as text files in a git repo. I used the ".jexp" extension to give Notepad++ something to key off of to know which syntax to use. I found it useful for times when I accidentally broke something and needed to revert an old commit, and it was easier than constant copy/pasting back and forth. If I needed to edit an expression I would just open it from the repo, make my edit, then do one copy/paste into MC. I might have to do that a few times if the expression wasn't correct. So anyway, would it be possible that Zelda could allow for saving/opening expressions that are saved as text files? Or open an entire directory and allow browsing for them in a tree, like you can with editors like VS Code, Sublime, etc? And then maybe a copy button to allow easy copy/paste into MC? If it did that I could easily browse for the expression I need, edit it, see the results immediately, all from within Zelda, and then only do a final copy/paste once I'm done.

zybex:
Hi Doof, thanks for the feedback :)

Those are good ideas - I initially had a couple of buttons for file load/save, but then I decided to just save the session state (list of tabs and their content) and thought that load/saving was redundant. But you have a point with GIT, it still makes sense to have it. I'll add this to the TODO, along with an optional file extension association (.jexp, you named it).

Button to copy the tab content - you just need to do CTRL-A/CTRL-C, but a toolbar button is easy to add. What I'd like to do, however, is load an expression from a given field (like "tooltip") into a tab, edit it, and then save it back to the field directly. Unfortunately the API doesn't allow me to do that yet, but Matt said he'll add the missing functionality eventually.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version