09-20-2013 02:46 PM
@JÞB wrote:
Clipboard operations need to expire the same way the dodo did.
You mean the last female clipboard operation going over the cliff to try to grab the last watermelon? (Ice Age 1 or 2, whichever)
Sorry, it's Friday afternoon...
Cameron
09-20-2013 03:12 PM
The clipboard is an effective means for user mediated intra- and inter-process communication. It is the last resort for programmatic IPC, ie. do not mess with the user's clipboard. I even resort to temporary files before the clipboard for that.
But, my point is that what LV does in its own house (ie. what developer's use) is far different than what LV-based applications can get away with in the real world. Try skipping clipboard support in your next app and tell the customer you think the clipboard is too old-fashioned and should go away. (and if said customer is me, start ducking. I wouldn't really be throwing something at you, it is just that your head may get in between an object in my hand and the nearest wall).
09-20-2013 05:01 PM
I read through this thread and I agree that this is a bug. I filed CAR 428102 for it. It is a non-standard behavior compared to other programs that allow ctrl+c or ctrl+x as shortcuts, and as Darin said, this is not a great experience for end users.
Thanks,
Jeff Peacock
Product Support Engineer | LabVIEW R&D | National Instruments
09-23-2013 02:55 PM
Clipboard is marginally effective (and unfairly limited)
But that's not the point I tried to make. The Point being Ctrl+C Ctrl+V work the way they always worked in LabVIEW. The mere issue that the behavior (with an empty clipboard) is out of line with other applications just does not register on my "Oh-**bleep**OMeter"
IDN Drivers billed as "Plug-n-Play Project style" that are poorly organized llb's rank higher in my opinion. Heck, fix the VISA.User Data bug first (and I don't often use that property) Clean up FTP, bring TDMS Viewer BD into spec, add some of the advanced string functions to the palattes, obsolete the RCM option to "replace case structure with stacked sequence."
R&D has better things to focus on.
09-23-2013 04:03 PM
Jeff, you will notice that I did not instruct NI to correct this bug ASAP. In fact, if you have a way to actually set the priority of what NI is working on, please let me know, as I would definitely have a long list to submit (not including the one reported in this thread, which is a minor cosmetic annoyance).
10-02-2013 05:45 AM
I guess not too many users today are familiar with the old dos-shortcuts of shift-insert, ctrl-insert and shift-delete. This thread remembered me of them, and they work. 🙂
/Y
10-02-2013 03:21 PM
Are you kidding?
Until I read this thread, I had never tried ctrl-c or ctrl-x with nothing selected (why would I?).
The level of annoyance that this bug causes is infinitesimal.
10-02-2013 04:38 PM
@paul_cardinale wrote:
Are you kidding?
Until I read this thread, I had never tried ctrl-c or ctrl-x with nothing selected (why would I?).
The level of annoyance that this bug causes is infinitesimal.
Why would you? Because there are a few programs out there that allow you to Ctrl-a Ctrl-c to quickly copy the entirety of a text block. Users try that in a LV app and get ac inserted somewhere in the string. That is how things get pressed with nothing selected.
Some of us endeavor to produce professional, polished software using LV and pay sufficient attention to details to be annoyed by this. Each little mess that I no longer have to clean up helps going forward. Bugs that propagate from LV into my programs are more annoying to me than bugs that only get me during development.
10-02-2013 04:42 PM
I don't get "ac" inserted when I try that.
10-02-2013 04:54 PM
@paul_cardinale wrote:
I don't get "ac" inserted when I try that.
Try it in run mode.