Forum Discussion
Why do I always get a error report when I click on variables user count?
- 3 days ago
I assume you are using the latest version of Storyline. I don’t think this error has anything to do with your system or setup. You may want to revert to the May 5, 2026 build (3.116.36838.0). Hopefully, Articulate will soon provide a fix for the Articulate.Design.Triggers.UI.VariableUseDialog.OnHandleCreated error, which causes the variable panel to crash when clicking the Use Count while Slider, Dial, or similar interactive elements and variables are inserted on a slide.
Steps to reproduce the error in the latest version:
1. Insert a Slider or Dial
2. Open the Manage project variables panel
3. Select the Slider or Dial variable
4. Click the Use Count number
The error does not occur if the affected project is reopened in a previous version of Storyline. The error also occurs when older projects containing Sliders, Dials, and their associated variables are opened in the latest version of Storyline.
I reverted to the May 5, 2026 build (3.116.36838.0), opened your project, and was not able to reproduce the issue.
I assume you are using the latest version of Storyline. I don’t think this error has anything to do with your system or setup. You may want to revert to the May 5, 2026 build (3.116.36838.0). Hopefully, Articulate will soon provide a fix for the Articulate.Design.Triggers.UI.VariableUseDialog.OnHandleCreated error, which causes the variable panel to crash when clicking the Use Count while Slider, Dial, or similar interactive elements and variables are inserted on a slide.
Steps to reproduce the error in the latest version:
1. Insert a Slider or Dial
2. Open the Manage project variables panel
3. Select the Slider or Dial variable
4. Click the Use Count number
The error does not occur if the affected project is reopened in a previous version of Storyline. The error also occurs when older projects containing Sliders, Dials, and their associated variables are opened in the latest version of Storyline.
I reverted to the May 5, 2026 build (3.116.36838.0), opened your project, and was not able to reproduce the issue.
Ned Cool! Was I supposed to send that code to them in the error window?
- Nedim3 days agoCommunity Member
CJLu Yes, I would advise you to do so. Can you also please share a screenshot of yours here so I can compare it with mine? I’m just curious.
- CJLu3 days agoCommunity Member
<?xml version="1.0" encoding="utf-16"?>
<ErrorReport xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<UserId>aid|080ac91f-75ab-4a57-9635-cdb1d867b28a</UserId>
<HardwareId>3TUUU-RGWQ9-KM1D1-S9AU4</HardwareId>
<Message>Object reference not set to an instance of an object.</Message>
<StackTrace> at void Articulate.Design.Triggers.UI.VariableUseDialog.OnHandleCreated(EventArgs e)
at void System.Windows.Forms.Control.WmCreate(ref Message m)
at void System.Windows.Forms.Control.WndProc(ref Message m)
at void System.Windows.Forms.ContainerControl.WndProc(ref Message m)
at void System.Windows.Forms.Form.WmCreate(ref Message m)
at void System.Windows.Forms.Form.WndProc(ref Message m)
at void Articulate.Windows.Forms.Metro.MetroForm.WndProc(ref Message m)
at LRESULT System.Windows.Forms.NativeWindow.Callback(HWND hWnd, uint msg, WPARAM wparam, LPARAM lparam)</StackTrace>
</ErrorReport>
Related Content
- 1 year ago
- 1 year ago
- 1 year ago