Nv: 2.2.6 (124) changes Bring-to-Front behavior in way that tempts data loss

[gouch]

Previously, triggering the Bring-to-Front shortcut (correctly) focused the search field. This meant you could trigger nvALT and begin typing your search immediately.

The latest release instead keeps focus inside a note, maintaining whatever text selection was last active. This means when you trigger bring-to-front and start typing your search, you instead type over the content of a note.

[ttscoff]

I'm seeing this as well and think it's worth fixing. I'll look into it.

-Brett

On 3 Nov 2016, at 12:29, David Gouch wrote:

Previously, triggering the Bring-to-Front shortcut (correctly) focused
the search field. This meant you could trigger nvALT and begin typing
your search immediately.

The latest release instead keeps focus inside a note, maintaining
whatever text selection was last active. This means when you trigger
bring-to-front and start typing your search, you instead type over the
content of your last note.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/ttscoff/nv/issues/411

[Zortrium]

This change is driving me batty. Reverting to the old behavior would be greatly appreciated.

[philrj]

Such a relief I'm not the only one. Accidentally adding bits of text everywhere and deleting sections of selected text from previous copy/paste. Been going crazy and probably annoying neighbors w/shouts of expletives at 3am. Def eager for fix or toggle to switch behavior.

[volt4ire]

@ttscoff where can I download a previous version of nvALT without this bug?

[Zortrium]

I reverted to a backup. This issue makes the current version a non-starter. I'm frankly surprised that more people aren't commenting here -- the whole point of nvALT in my workflow is to save time by quickly jumping to the appropriate note using bring-to-front then search (keyboard only). Using the newest I'm forced to use the mouse to reselect the search bar each and every time.

But yes, there should absolutely be a link on here to the old version.

[ttscoff]

Version 2.2b106 http://abyss.designheresy.com/nvaltb/nvalt2.2b106.zip

The bug you're referring to is already fixed and will be out in an
update today or tomorrow.

On 7 Nov 2016, at 16:16, Robert Barat wrote:

Where can I download a previous version of nvALT without this bug?

You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/ttscoff/nv/issues/411#issuecomment-258980763

[ttscoff]

Or you can just hit ⌘L.

On 8 Nov 2016, at 13:04, Zortrium wrote:

I reverted to a backup. This issue makes the current version a
non-starter. I'm frankly surprised that more people aren't commenting
here -- the whole point of nvALT in my workflow is to save time by
quickly jumping to the appropriate note using bring-to-front then
search (keyboard only). Using the newest I'm forced to use the mouse
to reselect the search bar each and every time.

You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/ttscoff/nv/issues/411#issuecomment-259228199

[Zortrium]

Never bothered to learn that shortcut. Thanks!

[gouch]

Thank you @ttscoff