Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tracking cursor disappears when logging excluded state behaviours v8.9 Windows #553

Open
Eyeless6 opened this issue Nov 17, 2022 · 1 comment

Comments

@Eyeless6
Copy link

Describe the bug

When loging an observation of an uploaded media file the tracking cursor should be running above the current events during the behavioural logging session. However, in version 8.9 the tracker cursor disappears as soon as a second state behaviour is logged that excludes the first state behaviour that is running at that time. Also, the behaviours don't seem to be in order of time anymore.

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'Open Project' that includes an ethogram with state event behaviours that exclude each other or create new project and set new state behaviours with exclusion matrixes
  2. Set "tracking cursor above current event" under preferences
  3. Start New Observation
  4. Upload Media File (I used absolute paths)
  5. Start Video
  6. Log state behaviour A (that excludes state behaviour B)
  7. Log behaviour B (that excludes state behaviour A)
  8. See error - Tracker Cursor disappears and logged new behaviours seem out of order. (Screenshots included below)

Screenshots

Shows list of affected behaviours and their exclusion matrix
Ethogram

Shows behavioural with the red tracking cursor
With red tracking cursor

Shows the disappearance of the tracking cursor and the changed order of the behavioural log
Without red tracking cursor and out of order

Expected behavior
The tracker cursor should automatically stay above the current event and the behavioural log should be in order of time.

Desktop (please complete the following information):

  • OS: Windows 10
  • BORIS Version 8.9

In case of crash copy the content of the boris_error.log file (before relaunching BORIS).
No crash

P.S. Thank you for making your awesome software available! I have just gotten started and find it very useful and intuative! :)
All the best!

@olivierfriard
Copy link
Owner

Hi,
I am not able to reproduce this issue.
Can you send me your BORIS project file and a detailed procedure to reproduce it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants