Multiple Issues- slow startup, cut/paste quirks, and more

[gigios]

It's true, the bug not always presents, and I didn't manage to isolate the exact conditions under which it does yet.

The bug is ALWAYS presents when the selection height is NOT a multiple of 4 pixels (for example if you select an area with height 400 all works, if you select an area with height 397 you lost 3 pixels).

[marty2010]

It's true, the bug not always presents, and I didn't manage to isolate the exact conditions under which it does yet.

The bug is ALWAYS presents when the selection height is NOT a multiple of 4 pixels (for example if you select an area with height 400 all works, if you select an area with height 397 you lost 3 pixels).

I tried using custom selection:
Left=186
Right=244
Top=28
Bottom=128

Created the selection then did right (one or two e.g.) arrow to move the selection to the right slightly.
Same problem, still lost the pixels.

So, I must have not used the correct multiple from Top to Bottom.

[-DJ-]

The bug is ALWAYS presents when the selection height is NOT a multiple of 4 pixels (for example if you select an area with height 400 all works, if you select an area with height 397 you lost 3 pixels).

That's exactly what I'm seeing too. I can reproduce the bug 100% of the time, unless the height is a multiple of 4 pixels!

Unfortunately I do a lot of pixel editing with background transparency for icons, so this hits me all the time with PSP X3 and I have had to revert back to trusty old PSP 8!

Steps to reproduce every time (here at least!)
1. Create a new 32x32 pixel image with raster background, RGB 8bit colour depth & transparent
2. Zoom to 2000% or so, and using the brush (B) with a size of 1 draw a 1 pixel high horizontal line anywhere in the image
3. Hit (S) for rectangular selection, and select around your line
4. Drag your selection to somewhere else in the image
5. As soon as you deselect (e.g. CTRL+D, click elsewhere in the image etc)....*boom* it's gone...

Promoting the selection to a new layer keeps your precious pixels, though if you now "Merge Down" without editing at least one pixel in your new Promoted Selection layer you'll lose it again. ("Merge Visible" works fine though)

I could use the described workarounds but it's a bit of a chore when you're pixel editting, far easier to revert to an older licence and not disturb the workflow!

[marty2010]

Is it the Selection height (Gigios said) or the Image height that must be a multiple of 4?

[marty2010]

Ok,

I see initially where I made an understanding error.

What I get is, so far in testing.
If the image size is 128x128 I can remove an even or odd selection (column) without any pixels lost.
If the image size is 127x127 the even and odd selection (column) is missing pixels at the bottom.

Here I removed one pixel vertical column from a 127x127 then 128x128 image.

[marty2010]

When I test DJ's.

A horizontal selection (paint brush line, 1 pixel, black) will disappear.

But, a vertical selection (paint brush line, 1 pixel, black) is moved OK (see screenshots)!

[marty2010]

For a 127x127 and image 128x128 image.

A 1 pixel horizontal line will disappear.

A 4 pixel horizontal line will move OK - screenshot.

[bewitched9]

I have the same problem losing pixels off the bottom of image.

I too discovered that promoting selection to new layer instead of floating prevents pixels from disappearing. It is a pain to have to do it this way script or not. Does anyone know of any fixes??

Thanks

Kathy

[-DJ-]

Unfortunately, no

I recently wiped the hard drive of my system and installed a fresh copy of Windows 7 x64, and PSP X3 was the first application installed afterwards. This didn't fix the issue, so I think it is safe to say it's not some esoteric mix of drivers and/or other applications that is causing the problem.

I contacted Corel support about it a couple of weeks back and have been told that it is a known issue, there is still no patch for the problem but the product engineers are "doing everything" to identify the root cause.

Hopefully their solution won't ultimately be to "buy X4"

[SystemVisions]

The reason so many of us use the layer cut and paste method is: "That's the way the tutorial taught us in several of the earlier versions." This was a non problem until X3 made an unnecessary change. This single problem has caused me many hours of productivity time and it seems like a simple patch to restore it to the previous state might solve the problem. Why should it be taking months to correct? And why do they have a new version called "X3 Ultimate" when the old version still has so many bugs? (Bugs, by the way, which are still present in X3 Ultimate).

[Leiana]

I am experiencing the selection bug also. I have played around with it for a while and discovered 2 interesting things:

1) It is not Nvidia only, as I tested it on another machine with an ATI card, and same problem occurred.

2) If you go to edit the selection using the edit selection tool then exit the edit selection tool and then deselect the object - no lost pixels.

3) There are no lost pixels when selection is on an Art Media layer

*edit*

I think this is a Windows 7 issue... just installed X3 on my laptop running Vista, no missing pixels!

I really hope they fix this soon as its getting a little annoying!

[-DJ-]

Leiana, thank you for the workaround, it works beautifully!!

I've created a script that simply toggles the Selections->Edit Selection setting, and then Select None.
If you then bind the script to Ctrl+D these steps are run instead when Selecting None and the pixels are retained.

Wow, I can use X3 for actually editing images for the first time since buying it 6 months ago!!

FWIW it's not just a Windows 7 issue - I suffered this issue all the time I had Vista as well (64 bit).

[Leiana]

Maybe its a 64bit issue then. My laptop runs vista home premium 32bit. I'm glad my workaround helped you.

*edit* I recorded and bound the script to ctrl+d just as you suggested - problem solved!

[-DJ-]

Ah, well that's something I can help with as a thank you!

I did think about attaching the script here but I figured folks would feel more comfortable if they created the script themselves (no worries about what else the script might do!). This looks complicated but it's not - I'm just covering every micro-step here!

1. With an image in PSP open, select an area (doesn't matter what as long as it's not empty)
2. Select File->Script->Start Recording
3. Select Selections->Edit Selection
4. Select Selections->Edit Selection again to turn it back off
5. Select Selections->Select None
6. Select File->Script->Save Recording
7. Navigate to the "Scripts-Trusted" folder (which is in My Documents\My PSP Files) and save it as AvoidSelectionBug.PspScript (Note I also unticked "Save Materials" and "Remove Undone Commands")
8. Now go to View->Customize and click on the Scripts tab
9. Under "Select a script and an icon to create a new binding" click the drop-down box and select the AvoidSelectionBug script (probably the third one down)
10. Click the [Bind] button and you'll see it appear in the "Bound Scripts" section below
11. Click on the Keyboard Tab, and under "Category" select Bound Scripts
12. In the "Commands" section select the AvoidSelectionBug script
13. Click in the "Press New Shortcut Key" input box and then press the CTRL + D key combination. If it recognises the keystroke it should say Ctrl+D in that box
14. Click the [Assign] button, and then the [Close] button...

That should be it! Now when you copy and paste or move something, when you hit CTRL+D it should de-select as normal but leave those precious pixels intact!

*edit* Didn't spot your edit but perhaps my shopping list will help someone else...

[lertulo]

DJ, thanks a ton for the walk-through; worked great!

I purchased X3 when it first came out, and immediately had to uninstall it and revert to X2 because of this lost-pixels-on-the-bottom bug. I complained to Corel and was basically told that my only recourse was to petition for a refund. Sigh. Been watching every update they offer to see if they've finally gotten around to fixing this, but apparently it's just not a very high priority.