Join free weekly webinars
Find us on

FAQ Blog

  • EventIDE utterly supports the XAML data binding that allows monitoring and modifying  variables and object properties at runtime via the XAML-based GUI. However, the XAML data binding mechanism has some limitations, which can be counter-intuitive in real-life scenarios. Here, we show you several workarounds for common binding problems in EventIDE. The workarounds are available in the latest EventIDE versions (starting from 03-Feb-2016).

  • Using C#, you can program virtually everything in EventIDE, but for many experimental methods it will be a reinvention of the wheel. There are many packages, e.g.  the Psychophysics Toolbox (PTB), that contain already a great number of implemented methods. The PTB is coded in Matlab and this article shows how to call any Matlab function (not only from PTB) in the new version of EventIDE.

  • The Arduino USB boards provide an easy way to communicate with an arbitrary electrical hardware by a computer USB port. The attached hardware may include LEDs, motors, sensors, response buttons, etc. Current Arduino models feature an USB interface, analog input pins and digital I/O pins and a programmable processor. Arduino boards can be used as low-cost DAQ cards in many research scenarios. This post describes how to communicate with an Arduino card in EventIDE. Consider, for example, that you want to control a LED attached to the digital pin 13 on an Arduino board. 

  • A movie file contains a stream of frames. Each frame can be represented by several hundreds thousands pixels. Usually there are 25 frames per 1 second of playback, so the movie files are condemned to be very large. To reduce a movie file size, various compression algorithms are used. Most of them are called “loosy”, because a compression process may discard or modify the original frame pixels. Although the results are barely noticeable while watching a video, the loosy compression can be disadvantageous, when a movie is used as experimental stimulus. The following example shows what may happen, when a movie is compressed with a standard loosy codec. You can see compression artefacts on the on the middle image. In contrast, when lossless codec is used, the frame pixels are intact (compare the left and the right images)

  • After positive feedback on first EventIDE webinars, we decided to carry them regularly, once per one week or two weeks. The webinars will be given by a EventIDE developer and you need just a web browser to join. We especially encourage new website visitors to attend the nearest webinar, in order to get more detailed information about EventIDE.

  • Imagine you ask a participant to run an experiment on his own, because … weather is too bad to go at work, for example. If  the participant does not know how to launch EventIDE, load an experiment and run it (a piece of cake for us, btw), he can easily break a 50 000$ research equipment. However, there is an easy solution- you can prepare EventIDE for running in the ‘player’ mode.

  • We offer perpetual  software licenses to EventIDE users. Each license is associated to a unique license key that is issued by Okazolab to a single user or user group. You need to activate a license with your key in order to leave the evaluation mode, in which EventIDE works by default. A license has to be activated on every computer, where you use EventIDE. License activation is an easy one-time process that can be done either online or offline. This article guide through all necessary steps.

  • In Windows you can always make copy the current screen into the clipboard, by pressing the Print Screen button. However, then you will need a graphical editor, where the clipboard data can be pasted and saved. Another limitation is that the clipboard can contain only one screenshot in time. EventIDE offers a better solution for taking screenshots, which is almost as easy, as pressing the Print Screen button. 


    First, navigate to the the HQ ribbon tab and browse the properties of the experiment in the property grid. Find the Save Screenshot property and add a proxy variable, to be able control the property in your code. 

    Whenever you want to make a screenshot of the current stimulus screen, assign a string containing a full file name to this property in snippets. The screenshot will be saved into the target file after the end of a snippet call. The format of the image file is defined by the extension of the file name: .bmp, .png or .jpg

    For example, consider the following code in the Triggered snippet of the Button element. The code saves  the current screen to a file after a button press:

    SaveScreenshot = "c:\\temp\\ScreenShot1.png"; // copy the current screen into a png file


    If you prefer to save screenshot images in other formats, like bmp or jpg, change the extension of file in the name:

    SaveScreenshot = "c:\\temp\\ScreenShot1.bmp"; // copy the current screen into a bmp file


    Note, that a string file name in C# is defined with double slashes.