Mon, Feb 18
I am new here and I am very motivated to invest !
Fri, Feb 15
Sun, Feb 3
Sat, Feb 2
Thu, Jan 31
Jan 21 2019
Thank you sir.
I will do it and i need some more information
and I'm new to this so it will be better if i get some guidance.
Jan 20 2019
Currently, the three main columns in Elisa interface cannot be resized by the user. The idea is to allow to resize them while keeping the current way of switching between views.
Hello Sir, I'm interested in this .
will you elaborate me want to be done exactly.
Jan 18 2019
Jan 16 2019
Jan 15 2019
Thanks for your work.
deactivate event filter when SPACE is not assigned as shortcut
Jan 14 2019
Everything there is pretty awesome!
maybe then we have to take a peek at it.
Ok i will do as you have mentioned. I had to handle return keys separately as they dont trigger actions.
Thanks for your work. It works really well.
Jan 12 2019
I have updated the diff. Elements focused using tab key will be triggered by Return Key. SpaceBar is assigned global shortcut for play-pause action and won't trigger elements focussed using tab key. Should work for most part.
Jan 11 2019
Ok lets look into it. It might be done through an ugly hack using event filters, but i have to research up a bit.
So maybe it should, or maybe using the space bar should continue to click the selected element when that element was selected using the tab key.
Yes, but elisa doesn't click the elements under focus even through the return key.
For example the mute/unmute button.
@ngraham can you please specify on which element did you navigate to. I tried to replicate it, it does as you mentioned, on the navigation action bar. But not on the elements outside it. And the purpose of the patch was to perform playpause action irrespective of focus. So probably blocking all the tab events of navigation action bar should do the job.
maybe i need to do the job using event filter instead of the usual shortcut mechanism used by Elisa
I notice that after navigating to an element using the tab key, hitting the spacebar does correctly trigger that element rather than doing play/pause, but then the just-triggered element is no longer selected afterwards. We should probably preserve that.
Added context to the diff. Thanks @shubham.
Ok i will start using archanist ASAP
I used archanist to apply the patch. It is working fine for me.
Made the shortcut configurable. I actually did a "git pull" and updated the feature out from a fresh repo. It should work now.
Ok, I will look into it.