top of page

EventIDE Q&A

Public·8 members

Screen caster not working properly (?)

Hello,


I am building an experiment using two screens: one for the participant and one for the experimenter. I want the screen caster to record the participant's screen.

When I run the experiment in Full-Screen mode, the screen caster records the experimenter's screen instead. However, in Preview mode, the participant's screen is recorded correctly. Running in Preview mode would not be a viable option, since random parts of the screen appear black during to stimuli presentation.


Does anyone have any insights on this?


Thank you,

Sofia

36 Views

Sophia hi,


EventIDE had an issue when it incorrectly swapped up the stimulus and status monitors in the full screen mode on some PCs. The issue can be related to your problem because the Screencaster element uses the same monitor detection procedure. Can you try to select the experimenter's screen on Screencaster, just to see if the screens get swapped again? Another possible solution can be in rearranging the monitors positions in Windows display settings- I would try to move the left monitor to the right and vice versa.


If nothing helps, can you book a support meeting with me, so we can look at the issue together?

EventIDE Black screen GUI mode

Hi!

I am building my first experiment in EventIDE.


Quick Experiment Overview: "The core of my experiment involves 2 renderer elements. My experiment works as follows: after some time the target element will become visible set by the proxy variable. After that the second object is supposed to recognize the target and calculate the difference of the distance between the two objects and will start moving towards the target. When it reaches the target it stops, and the color of the target is supposed to change."


This worked perfectly and smoothly until yesterday night. I tried to add some additional features like a button press to make the target appear manually, and use a text element to display information if the time has run out. After implementing this, the experiment didn't work anymore --> black screen. I removed all the new parts I had implemented, but the black screen remains…


135 Views
Ilia Korjoukov
Ilia Korjoukov
Oct 31, 2025

Bela hi,


It sounds really weird but we had some rendering issues with laptops that have double graphic cards. Can you, for the start,send me your task, so I can run and check it here? My email is info@okazolab.com

EventIDE crash when selecting "Multiple Datasets" after pinning two charts

Hello,


I am building a model where I want to visualize multiple custom variables in the same chart. For example, I want to plot one custom variable against another to visualize their relationship.

My variables are manually coded proxies via snippets, not linked to built-in element signals.


I haven’t tried the Multiple Channel Analyzer for multiple datasets yet, because for single datasets I already had difficulties plotting manually coded proxies in the screen editor, although the single-channel analyzer did allow selecting these proxies.


Instead, I pinned two charts, which gave me access to the configuration of multiple datasets in a chart’s properties, but that’s when the bug occurs.

Whenever I click on the dropdown menu to select a dataset in the pinned chart, EventIDE immediately crashes and closes. This happens consistently when trying to access multiple datasets.


57 Views
Ilia Korjoukov
Ilia Korjoukov
Oct 30, 2025

Mathilde hi,


I will check the crash in chart asap, but there is another even better solution. You can convert your numerical variables into continuous signals with the Proxy Variable Signal element in EventIDE. After that, you can plot such variables with Multiple Channel Analyzer, record them along other real signals or do some signal processing.

Build/compile errors with shared Header variables, Duration access, and C# feature support in EventIDE


Dear Community,


I’m building my first closed-loop go/no-go experiment in EventIDE using a cybernetic layout (Sensor → Comparator → Controller → Actuator) on the root layer, and I’m encountering a few blocking compile/runtime issues that I can’t quite explain.


Bug 1 — “inaccessible due to its protection level”


After a clean save, (without any compilation error indicated within any snippets) the global banner reports snippet compilation errors, and I get:


“DynamicSnippetAssembly.clHeaderOnlySnippetHub.W is inaccessible due to its protection level.”


However, W (a constant representing the size of a sliding window used in my model) and the sliding-window state (Queue win, winSum, mean_win_ms, err_ms) are all defined once in the header and used across events.


98 Views
Ilia Korjoukov
Ilia Korjoukov
Oct 30, 2025

Hi Mathilde,


I will try to comment on all point below.


Bug 1 — “inaccessible due to its protection level”

When you declare variables in the Header snippet, EventIDE wraps them with additional change-tracking code. In some cases—especially for complex types—this wrapping can fail, leading to confusing compile errors that actually originate from the generated wrapper code.

If that happens, you can add the internal keyword in front of the variable declaration, for example:

internal int i = 5;

This tells EventIDE to skip wrapping for that variable, which usually resolves the compilation issue.


Bug 2 — Duration property not visible from snippets

None of the element or event properties are directly accessible by default. You need to create proxy variables (via the “+” button in the property panel) for each property you want to access from snippets.

Note that you can also create proxy arrays or proxy hub variables linked to multiple objects — just select several objects before creating the proxy variable.


C# syntax support

Good catch. EventIDE should automatically use the most recent C# compiler compatible with its .NET 4.8 core (i.e., C# 7). However, in practice, the current version still defaults to the older C# 5.0 compiler, which explains the missing support for string interpolation and newer syntax.

We’ll fix this in the next update — but if you’d like, I can send you a patch right away.

bottom of page