Persistence across routes about angular-hotkeys HOT 7 CLOSED

First of all, that is an excellent sombrero and I applaud your profile picture.

secondly, (and maybe more importantly), I guess I viewed controller defined hotkeys as being persistent because people using them likely aren't using them in conjunction with routes. You raising the issue means this may not be the case. Can you help me with a use-case so I can wrap my brain around such things?

from angular-hotkeys.

My feeling was (could be totally wrong, but at least for people using ngRoute - though don't know what fraction that is anymore) that most controllers are tied to a view, and in most cases that meant instantiated on a route change. I realize that may not be the case for others, but I have built several simple apps around that idea.

I would be happy with a provider config option to not persist them by default...

from angular-hotkeys.

+1, I feel that if anything persistence should be manually declared

from angular-hotkeys.

+1, I agree. The sombrero rocks. Additionally I agree that it would be nice to exit a route and then have the hotkey continue to work once returning to said route. I was so excited to see that the hotkeys could be defined at the route level. I'm going to wire it up to the controller for now but will switch it out if you decide to add this.

from angular-hotkeys.

Hotkeys defined by routes are not persistent so it sounds like your usecase
will work without modification.

from angular-hotkeys.

Hmmm,

When I first call the route everything works but when I leave the route and
return, it stops working. I solved the problem by binding to scope in the
controller.

On Wed, Jul 9, 2014 at 11:35 AM, Wes Cruver [email protected]
wrote:

Hotkeys defined by routes are not persistent so it sounds like your usecase
will work without modification.

—
Reply to this email directly or view it on GitHub
#11 (comment)
.

Bill Butler
[email protected]
(615) 330-5044

from angular-hotkeys.

Sorry for the delay here, I'm trying to clean up old tickets. This scenario is likely possible using the newer bindTo syntax

from angular-hotkeys.