You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey @sjjhsjjh hope you don't mind me starting a feedback thread!
My main question is not particularly around the technology or the approach taken but more a bigger question about building input into Dasher.
For me this should not live in Dasher. Mainly because its really cool so we shouldn't limit it to only work in Dasher. This should be an independent PC input method, that way it can be used with any communication software or just the computer in general.
I think we should spend as much effort as possible making our input APIs as flexible as possible so that things like this can easily be used to control dasher but not be build in directly to the application. There are too many different input methods a user can use and infinitely more configurations that we couldn't possibly be able to build them all into the application so we shouldn't even try, leave that to specific input methods to do.
Switch controls are quite expensive.
This is an unfortunate reality. Lots of specialised hardware is this expensive. If we decide to include this in Dasher would we then want to have our own cheaper eye tracking system? It really quickly increases the scope of dasher.
I don't want to seem discouraging! All of these ideas are great! I just think that we should make sure that users can get the most out of the innovations you are suggesting.
The text was updated successfully, but these errors were encountered:
Hi Gavin, Thanks for your interest and time in responding. I agree that the ideas here aren't specific to Dasher. Is there another project that the repository should move to?
Hey @sjjhsjjh hope you don't mind me starting a feedback thread!
My main question is not particularly around the technology or the approach taken but more a bigger question about building input into Dasher.
For me this should not live in Dasher. Mainly because its really cool so we shouldn't limit it to only work in Dasher. This should be an independent PC input method, that way it can be used with any communication software or just the computer in general.
I think we should spend as much effort as possible making our input APIs as flexible as possible so that things like this can easily be used to control dasher but not be build in directly to the application. There are too many different input methods a user can use and infinitely more configurations that we couldn't possibly be able to build them all into the application so we shouldn't even try, leave that to specific input methods to do.
This is an unfortunate reality. Lots of specialised hardware is this expensive. If we decide to include this in Dasher would we then want to have our own cheaper eye tracking system? It really quickly increases the scope of dasher.
I don't want to seem discouraging! All of these ideas are great! I just think that we should make sure that users can get the most out of the innovations you are suggesting.
The text was updated successfully, but these errors were encountered: