Page 1 of 1

Colors messed up when inserting Screenshots

Posted: Sat Nov 17, 2007 11:27 am
by Guest
Hello everyone,
I "take" the usual screenshots with the Print-Button.
When I want to insert this screenshot with CTRL+SHIFT+V into XnView, it looks like this:
Image

How can I fix this?

(My video card is a ATi X1400.)

P.S.:
I'm sorry I didn't register, I'm just tooo tired to go through the whole process right now.

Posted: Sun Nov 18, 2007 11:12 am
by foxyshadis
Xnview has always done very strange things with print screen when it's open, for me, though I never got around to reporting it. Oddly, I have the same card, though it occurred on a 9200-based laptop as well. (I get 1-bit monochrome output, not even 8-bit like you.) The only way you can get good screenshots while it's open is to use xnview's screen capture utility (Tools, Capture Screen), not the system's.

I suppose it would have been a good idea to mention this a while back.

As an aside, this function really needs a shortcut, and also really needs to have the print screen key itself in the list of hotkeys. I mean, it only makes sense, and it's no harder to hook.

Fixed in last

Posted: Sun Nov 18, 2007 5:28 pm
by Clo
:arrow: Guest

:) Hello !

• I use PrintScreen and also Alt+PrintScreen a lot in XnView,
for instance to make images for the Manuals, and that works in the last 1.91.6.

• There was a bug like you show (or very similar) in previous versions1.9xxx that I reported HERE.
- It's fixed, I checked that again now.
- However, a minor bug remains : in some cases, when you have set a button for the “Import Clipboard” function
and want to paste a capture of XnView itself just made before, that button stays grayed while it might be enabled.
- That works from the menu, though…
- I've an onboard video with an Intel mother-board, and set 16 BPP only @ display.
- The bug occured with that colour depth only, like said in the French thread linked above.
- XP-Pro SP1 (FR-Eng.).

:mrgreen: Kind regards,
Claude
Clo

Re: Colors messed up when inserting Screenshots

Posted: Mon Nov 19, 2007 8:01 am
by xnview
Anonymous wrote:Hello everyone,
I "take" the usual screenshots with the Print-Button.
When I want to insert this screenshot with CTRL+SHIFT+V into XnView, it looks like this:
Which version do you have?

Posted: Mon Nov 19, 2007 1:28 pm
by oops66
Hello,
It works on Win98SE (for windows 16 and 32 bit screen display), maybe it's an OS related bug with XnView ? (for the gray color ?)
Like here : http://newsgroup.xnview.com/viewtopic.p ... &highlight

Posted: Mon Nov 19, 2007 5:41 pm
by helmut
Could you please tell us the Windows version you are using?

What's the numer of colours /colour depth used on your system (Right click on free area on desktop, menu item "Properties", Folder tab "Settings" shows the value)?

Posted: Tue Nov 20, 2007 10:05 pm
by enrico
helmut wrote:Could you please tell us the Windows version you are using?

What's the numer of colours /colour depth used on your system (Right click on free area on desktop, menu item "Properties", Folder tab "Settings" shows the value)?
Hello everyone und juten Abend Helmut.

I'm the one "invité" who started the thread.
Long story short: Accidently reading only Helmut's post, I thoght I might try changing the depth to 32bit (yes, it was set at 16bit before) and then re-do everything. It worked, so thanks for suggesting indirectly it might be the colour depth. :)

Some facts, if anyone's interested:
XnView Version: 1.91.1 (Jun 11 2007)
OS: WinXP SP 2 + all updates available (in German, of course)

Plz upgrade

Posted: Tue Nov 20, 2007 11:50 pm
by Clo
—> enrico

:) Hello ! Welcome aboard as a Member !

• You might upgrade to 1.91.6 because that bug is totally fixed (except the minor issue I describe above).
No more problem with 16 BPP now.
- 1.91.1 had the bug with 16 BPP, and strangely, when you switched from 32 BPP to 16 BPP, the bug didn't occur.
- We had it only when booting Windows with 16 BPP already configured before…

:mrgreen: VG
Claude
Clo

Re: Plz upgrade

Posted: Sun Nov 25, 2007 12:23 pm
by enrico
Clo wrote: • You might upgrade to 1.91.6 because that bug is totally fixed (except the minor issue I describe above).
Hi Clo, thanks for the nice welcome!
I just upgraded, so everything should be working fine ... :)
See you!