4. I keep getting an occasional exclamation "Ping" and the Comunication" box says I have a duplicate, when in fact I never did a Ctrl+C to create a duplicate.
Example:
Quote
17:59:31 Isduplicate NF and CHS clearly can't comfortably coexist
17:59:31 newItem() duplicate - skipped
An informational/debug message, due to the way CHS "re-establish clipboard periodically"
5. I have found the "Comunication" box (missing an "m" there) very informative for testing purposes. I think it could be useful to retain that function, to provide a background log and for the user to enable/disable it for monitoring/testing purposes. Having a Copy button on it is a good idea too, as you can choose whether you want to keep part/all of the current log in the Stack - arguably better than having it as a separate log file, at any rate. (Though there seems to be something slightly amiss with the "Comunication" box - see "Minor issues" , below.)
It could be useful during testing, but, as mentioned, it's not quite ready for prime time yet
1. There is no tooltip for the help, tools and utilities toolbar button - not sure if you wanted there to be one. (This is as per oblivion's comment.)
fixed
2. Though the position of the MAIN NF UI window seems to be remembered OK by NF (from its last opened position on the screen), some of the popup windows (e.g., Options) opened from the UI seem to open with their lower part truncated by (or "below") the bottom of my laptop screen. If I drag the popup window to where I can see it all, and then close it, the next time I open that popup window, NF evidently doesn't remember where I last moved it to - the window starts off again in the same truncated position. (This is as per oblivion's comment - sorry, though I had noticed this a while back, I had forgotten to mention it until I was reminded by his comment.)
Correct - most child windows are positioned relative to the main window. I'll move the options window up, but it won't be set to remember it's position in this release.
3. The "Comunication" window (missing an "m" there) is intrusive - this seems to be because, the way it currently works, it sometimes steals window focus, which it probably should not be doing. (Similar to what was mentioned by oblivion.)
See comment above
3. You sometimes/always (it's repeatable anyway) seem to have to force a Stack/viewer refresh (Ctrl+R) before a recently-copied clip with the search term appears in the search. It's in the Stack, but just not appearing in the search until you refresh. (Similar to what was mentioned by oblivion.)
Correct. At present, a search is "static".
I'll correct the issues as mentioned above and put a new version out. Unless I screw something up in the process (as we've seen, very possible), we MAY be getting close to a release.
Show Posts
