PI Selection Tool - Question?

Post Reply
mdb123

PI Selection Tool - Question?

Post by mdb123 »

I have been using PI for about 4 years, love it. Use it 7 days a week. I've had some small issues, but managed to either fix them or work around.

I convinced my partner to buy PI11(which I also have). She has had major issues since downloading the software. Most of them I've managed to fix for her. But now I am stumped!

Her 'selection' tool doesn't work properly...strangest thing I've seen.
To try to resolve her problem, we've both run our software at the same time and used the same images to work on. We've compared our settings, tools , etc. everything seems to match 100%. Yet, when she uses the Lasso tool, it doesn't work properly. It will outline her selection, but when she clicks inside the selected area, she cannot move the object, and gets lines projecting out from the center of the cursor! Then she cannot move her cursor outside the selection either , not even to click Edit-Undo. It gets stuck.

Even stranger. If she does use the Lasso to create a selection, and just creates a selection, but does not click on the selection, but simply uses the Edit-Copy function, she can then copy that selection to another background. But once it has been copied there, she cannot move it..again, the mouse cursor doesn't seem to work inside the 'selected' area...

Since I've never encountered this myself I am at a loss as to why this happens? Has anyone else experienced this problem, if so, how did you fix it, or get around it? Her only option now is to use the Extract Object function instead, but that really is not what she wants to do.

I'd be thankful for any suggestions....'we' are both puzzled on this one.


:roll:
User avatar
Ron P.
Advisor
Posts: 12002
Joined: Tue May 10, 2005 12:45 am
operating_system: Windows 10
System_Drive: C
32bit or 64bit: 64 Bit
motherboard: Hewlett-Packard 2AF3 1.0
processor: 3.40 gigahertz Intel Core i7-4770
ram: 16GB
Video Card: NVIDIA GeForce GTX 645
sound_card: NVIDIA High Definition Audio
Hard_Drive_Capacity: 4TB
Monitor/Display Make & Model: 1-HP 27" IPS, 1-Sanyo 21" TV/Monitor
Corel programs: VS5,8.9,10-X5,PSP9-X8,CDGS-9,X4,Painter
Location: Kansas, USA

Post by Ron P. »

Hi Mdb, and welcome to the forums..:)

Since you don't have this issue on your system, what is different between the two systems? I would first look at the mouse. What type of mouse are you using and is it the same as hers?

There seems to be something with PI and her mouse that is not communicating properly. Try to check to see if the software for the mouse is updated. If you have any software that is used to install the mouse, try reinstalling it.

This may be a problem with PI, but maybe doing this will shock PI into talking nicely to the mouse, and stop being rude...

Aside from that, would be doing a repair or reinstall of PI..

Ron P.
Ron Petersen, Web Board Administrator
sjj1805
Posts: 14383
Joined: Wed Jan 26, 2005 7:20 am
operating_system: Windows XP Pro
System_Drive: C
32bit or 64bit: 32 Bit
motherboard: Equium P200-178
processor: Intel Pentium Dual-Core Processor T2080
ram: 2 GB
Video Card: Intel 945 Express
sound_card: Intel GMA 950
Hard_Drive_Capacity: 1160 GB
Location: Birmingham UK

Post by sjj1805 »

First thing I would try is an uninstall - reinstall.
mdb123

Post by mdb123 »

Thanks guys for the welcome, and quick replies. As for our Operating systems, we're both using Windows XP. Her's is Pro, mine is Home Edition. Other than that we're the same.

I do know that I use a laser mouse, not sure if her's is laser or 'wheely'. But I will check on that.

We have already tried the uninstall and reinstall 2 times. The problem still remains, although the reinstall did fix some of the other annoying bugs.

I do think it might be something systemic rather than specific to PI though. I know she describes the 'type' of cursor she sees as being an 'X' with a small square underneath..I don't see that when I am doing the same step. I get an 'X', but mine looks more like a crosshairs, no little box. In any case we will continue to try to sort this out. If anyone else has any thoughts I'd be very pleased to hear them.

I spent months convincing her that PI was 'so much easier' than using Photoshop...now she is ready to throw it out the window.......after only a few days!
sjj1805
Posts: 14383
Joined: Wed Jan 26, 2005 7:20 am
operating_system: Windows XP Pro
System_Drive: C
32bit or 64bit: 32 Bit
motherboard: Equium P200-178
processor: Intel Pentium Dual-Core Processor T2080
ram: 2 GB
Video Card: Intel 945 Express
sound_card: Intel GMA 950
Hard_Drive_Capacity: 1160 GB
Location: Birmingham UK

Post by sjj1805 »

It does appear a bit strange.
Have you checked if this mouse problem exists in any other software or is it only affecting PhotoImpact.

If only photoimpact, I realise you have uninstalled-reinstalled twice already but try our method here:
http://phpbb.ulead.com.tw/EN/viewtopic. ... 5638#55638

If other programs are being affected go to the Windows control Panel and you will see an icon for the mouse. Check the settings here.
If tht doesn't cure the problem go to the hardware manager and uninstall the mouse. Reboot and the mouse will be re-detected and re-installed.
does this cure the problem?

Most 'mice' rely on the drivers built into Windows XP but there are some that have extra functions and require special drivers. Did the mouse come with a driver disk. If so go to the hardware manager again and try updating the drivers - using the disk that came with the item.
mdb123

Post by mdb123 »

Thanks, I will look into all of the items you mentioned. I believe the mouse being used came with the PC and the drivers are the originals included with the standard XP software. But I'll ask my partner about that. It could be a conflict of some sort. I do know that she does not have this problem when using her Photoshop application, only in PI. But will wil check the systems info first, and if need be, will reinstall anything that needs updating.

Thanks again for all of the very detailed and helpful advice. :) :wink:

Update on my previous post. Problem resolved. Not sure what we did right, but we got it fixed. Thanks for all of your advice :)
Post Reply