Dynamically disable seek by click

[chris-saunders]

Description

I would like an API point to be able to toggle the users ability to seek by clicking on the score.
I see that in the master branch there used to be a setting to disable seeking, but it seems that has since been removed.

Possible Solutions

Add a setting to enable/disable seeking, that we can then update with the update settings call.

Current Workarounds

None that I am aware of

[Danielku15]

Yes, I lately simplified the logic within alphaTab regarding the click handling and by this removed the setting. I decided to connect the cursor setting with the availability of user interaction.

But if you need this feature, I can easily bring it back.

[chris-saunders]

Thank you very much it would be appreciated.
Would you also be able to add an event for when a user seeks? Or would that be a separate feature request?

[Danielku15]

Would you also be able to add an event for when a user seeks? Or would that be a separate feature request?

Technically yes. But I might get it wrong so to clarify:

You want to disable the default selection and seek-on-click behavior (initial request).
But you want to capture (with this default behavior disabled) that a user clicked on a beat/bar to handle it on your own (second request)?

Or is your second request that you want to capture the default "seek-on-click" if it is activated?

[chris-saunders]

You want to disable the default selection and seek-on-click behavior (initial request).

Correct. A setting or some option to disable seek on click would be fantastic.

Or is your second request that you want to capture the default "seek-on-click" if it is activated?

That is more what I was thinking of. Personally for my use case it would be excellent to be able to tell when a user seeks by clicking, and do things based on them seeking.

Sorry for the lack of clarity, and thank you!

[Danielku15]

Okay, I will check how to add this feature best. Maybe I will just add a "beat clicked" event which handles both scenarios. If the default user interactions are enabled, the beat click will request a seek on the player, if it is disabled, the event can still fire and the developer could decide what to do.

The main thing that made it confusing for me was that you ask for an option to disable the default seek-on-click feature, but then at the same time you want to have it active and get an event.

But I simply guess there are some conditions on your site to decide whether the seek-on-click should be active or not (maybe even dynamic).

[Danielku15]

The option and events are added in version 0.9.7.302.
Setting to configure the seek on click and selection: Player.EnableUserInteraction
Events related to click on beats:

• BeatMouseDown
• BeatMouseMove
• BeatMouseUp

I hope with this you can realize your needs.