I'm using Corel since the moustache guy (old Corel logo in the early 90s), so it would be around 1994 I guess? Really, I don't know whay is happening lately with the way you test the quality of your products. 700 bucks for a whole suite that is sold like a beta, is something dissappointing. I don't want to be harsh but I think I must complain.
For example, Corel Capture X7 !!!! don't work at all.
I've been complaining for long time ago, even in Facebook that when this utility capture the screen, it capture also an ugly black line on one of the sides, if I don't remember bad, is that right or left side. In other words, is capturing the frame that mark the area to capture, so it is capturing outside the selected area.
This bug comes from X4 I think and continue in X5, X6, X7 and will continue forever, seems to be.
ALSO THE ETERNAL PROBLEM: This hotkey is being used already by this system. Please choose another one.
Impossible to fix this. You can try all the possible combination of keys, and you will get always the same reply, all the keys are taken.
Fake, that is not true, I know all the keys I'm trying are not taken, but Corel Capture X7 don't allow to use new keys.
Is there any solution for this?
If you don't plan to fix this and the utility just simply don't work, why do you attach it to Corel Draw X series suite? Just simply kill it, and don't offer it anymore to your users, because it is taking hard disk space, and it is completely useless... unless you prove me, please, there is a solution for this.
What people says in forum is: USE TECHSMITH SNAG IT, which by the way is an amazing utility, but if I have my Corel Draw Suite X7 and I have my Corel Capture X7, I should be able to use it, so I don't understand why you offer something that simply don't work sometimes.
Cheers,
The capture problem is almost certainly a problem with your machine, not a Corel problem.
If a program is indeed capturing all the function keys, then you need to find out what program that is and tell that program to release at least one of them. Or perhaps Windows is wrongly telling CorelDraw that the function key is not available. Either way there is nothing that CorelDraw can do about it. CorelDraw can ask to trap a key, but if windows refuses to do so (on some machines, but not on most of them), then its not Corel's fault.
If its a laptop, the problem may be simple. Laptops often assign special hardware functions such as brightness and volume to various function keys -- theoretically to be used with another key such as Fn -- and then in their infinite wisdom deliver the laptop preconfigured to reverse the state of the Fn key -- so that it by default operates the hardware functions and you have to press Fn to make the F-keys work "normally". It is an option that will be configured in setup somewhere (the machine's setup, not Corel's) and you will probably find it by googling the laptop model number.
There is a second problem, which is Corel's fault. Corel uses the same default F key (F7) for capture and for What the Font. The WTF key is not configurable, but the capture key is. So, you can change the capture key to shift-F7 and leave the F7 key available for WTF it you want to use them both.
But you don't have that problem (yet) if you're not managing to get capture to work at all.
I use Capture daily and often here on x7 without any issues at all and I use the default F7 key. I am using a laptop with Win7 64bit. If you do not launch Capture first then F7 has a windows shortcut function. Launching Capture trumps that. Sounds like you might need to clean up the registry and window's temp files?
I just captured the screen here to double check with v7
First, let me point out I am not Corel, I am a user -- like most of the others here, unless they have "COREL" against their name when they post.
Next, that I have never had a problem with capture in X4, X6 or X7 on any of my machines. That doesn't mean I don't believe others have capture problems -- I have read most of the posts here for the last two years and I can see that some people do. But because I read most of the posts, I can also see that most of those who have managed to solve the problem have done so by accepting the possibility that the problem might be caused by either their hardware or other software.
So, let's try to be a bit more positive ... and start with a possible misunderstanding.
Most programs only use function keys when the program itself is in the foreground. You press F5 to refresh the browser screen, but you only do it when the browser is already the active program. When you are in some other program, pressing F5 does not refresh the browser, it may do something in the other program but even if it does not, it will not refresh the browser. This happens because the default windows behaviour is to direct all keystrokes including most function keys to the foreground program.
Capture is somewhat different. Capture works as a dormant background task. A function key assigned to capture must wake up the capture task when capture is not the foreground program -- otherwise you could only ever capture the output from capture itself. Programs do not usually receive keystrokes intended for other programs. Therefore, capture must ask windows to notify the keypress even when another program is active.
So ... the above may take a bit of understanding, but it is crucial to the problem. Allocating a function key for use entirely within the same program is something that is entirely within the control of that program. It does not need a special hook in windows. Consequently, a program can assign a function key without testing the notification mechanism that a background task such as capture requires.
Next problem is that windows seems to be able to notify one program about each function key. That's logical -- you probably would not want two things to happen when you press a function key. So, windows will only allocate each function key to one program.
What then if some program actually asks to be notified of all function keys, whether it needs them or not? That is at least one possible reason for capture to be unable to allocate a key.
You may ask what kind of a program needs to intercept all function keys. The answer is probably no program needs that many, but it seems that some programs do it anyway.
You mentioned Techsmith Snag-It. At least one user returned to say that it was an expired trial of snag-it that was stopping capture from using F7. So if you have ever installed that, it would be useful to try again after very thoroughly uninstalling all traces of it.
Next, there's a free download of Windows Hotkey Explorer at http://hkcmdr.anymania.com/ which gives an instant display of the keys reserved by various programs. Here is part oif it, showing that Capture has reserved shift-F7, which is the configured key on my system:
I really appreciate all the efforts and consideration showing possible solutions, but as I s aid, this is not a problem of assigned keys in Windows, in other words, the keys are not assigned in windows, the keys are free and ready to be used, however, a bug in Corel Capture make impossible to assign any key to it.I will demonstrate that Corel Capture fail always and Techsmith Snagit won't fail.In this 3 minutes video, you have a complete demonstration of what I said, and the proof that Corel Capture has a bug and make impossible to assign any key to it.Whilst in Techsmith Snagit you can assign the hot key you want for capture, F7 or Shift + F7 or Ctrl + Shift + F7 (all them will work), in Corel Capture you won't be able to assign any hot key, all them will fail.SO... if I can assign Shift + F7 in Techsmith Snagit and it work fine... it is clear and demonstrated Windows neither other program is using this hotkey combination...When I assign this hotkey in Corel Capture, it fails, and it fails, because the problem is in Corel Capture.Is not windows, is not other software be using this hot key combination, is a bug from Corel Capture.VIDEO PROOF, HERE:http://youtu.be/qZ4hona-qv8