[Wine]IPTC keywords bug into Preview IPTC Tab

[oops66]

If I add some IPTC keywords to a picture (Crtl+i \ "keywords tab"), no problem, I can see them into the preview window into IPTC Tab.
But if I also add in "Date\Time tab" a date in the field "Date Created(YYYYMMDD)"=20080801 then I can not see anymore the keywords in the preview window, I only can see a "+ keywords" with an empty field.
(and impossible to extend the tree structure with the "+")
And I can not anymore "clear" this field: "Date Created(YYYYMMDD)"
See .jpg samples bellow:
1: jpg1 = only IPTC keywords =xnview, jpeg -->OK

2: jpg2 = IPTC keywords + IPTC "Date Created(YYYYMMDD)" --> Problem

FYI:I have also this "+" problem with some others IPTC Tags: topic in French

[xnview]

Do you have the samples?

[oops66]

Do you have the samples?

Yes, the 2 .jpg just above

[marsh]

Do you have the samples?

Yes, the 2 .jpg just above

For me, IPTC info from samples are shown in preview.

[oops66]

...
For me, IPTC info from samples are shown in preview.

Very strange, because I can only see the first one in the preview IPTC tab !
sample N°1:

sample N°2:

And I can not play with the "+"

[marsh]

And I can not play with the "+"

I think that is a problem when using wine without a native comctl32.dll. If that is how you're using program, there are a number of things which won't work as expected.

[oops66]

And I can not play with the "+"

I think that is a problem when using wine without a native comctl32.dll. If that is how you're using program, there are a number of things which won't work as expected.

Thanks Marsh, you are right - bravo !
That's works under my Windows98SE system with the v1.94.2.
So the problem probably comes from the inclue Wine dll.
But I have tried the native one (from Windows98SE and also XP comctl32.dll ) but I have a crash with them.

I have also tried with winetricks, better but without success too.
http://wiki.winehq.org/winetricks

...For me, IPTC info from samples are shown in preview...

On which system ?
Do you have the same problem with Wine and your Win2000 comctrl32.dll ?
And if not, what is the way to solve this problem ?

XnView with Wine:
http://appdb.winehq.org/objectManager.p ... n&iId=1927

So for the moment, this post is Canceled.

[marsh]

On which system ?
Do you have the same problem with Wine and your Win2000 comctrl32.dll ?
And if not, what is the way to solve this problem ?

I'd try using an older version to first create the settings, even though that isn't the one which will ultimately be used.

Ex:
Settings originated by a recent (1.0) version > native dll isn't used.
Originated by an older (0.9.25?- 0.9.53) version > native dll is used (as expected and configured by winecfg).

[oops66]

Thanks Marsh

Code: Select all

I'd try using an older version to first create the settings, even though that isn't the one which will ultimately be used.

Do not do that for the moment, because it's probably not needed in my case.
My Wine version is always up to date (today: the v1.1.2)
And an older Wine version is not better for me with XnView.

Which Wine version do you have ?
And do you have this problem with the recent Wine version v1.0 or superior ?

Code: Select all

Originated by an older (0.9.25?- 0.9.53) version > native dll is used (as expected and configured by winecfg).

Yes I know, I have already tried this (without success), with the older versions but also with the v1.1.2 because this problem persist on my system.
( too many native comctrl32.dll version exist, I just need the good one - perhaps ?)

[marsh]

With v.1.0, the dll began working after I removed version number from text file below:
"/home/user/.wine/drive_c/windows/winsxs/manifests/*.manifest".
(Version="") or similar.

[oops66]

With v.1.0, the dll began working after I removed version number from text file below:
"/home/user/.wine/drive_c/windows/winsxs/manifests/*.manifest".
(Version="") or similar.

With into your "Winecfg" for the XnView entry : behavior = Windows 2000 and any natives .dll ???
FYI:
I have try to do this into my *.manifest file, but without success..
And I have not this problem with the XnViewMP0.015 Windows version under Wine too, so maybe it's not only a Wine problem ?

I have also deleted my .wine directory, and recreated it by using "Winecfg" (Configure Wine), but without success too, this problem persist.

[marsh]

With v.1.0, the dll began working after I removed version number from text file below:
"/home/user/.wine/drive_c/windows/winsxs/manifests/*.manifest".
(Version="") or similar.

With into your "Winecfg" for the XnView entry : behavior = Windows 2000 and any natives .dll ???
FYI:
I have try to do this into my *.manifest file, but without success..
And I have not this problem with the XnViewMP0.015 Windows version under Wine too, so maybe it's not only a Wine problem ?

I have also deleted my .wine directory, and recreated it by using "Winecfg" (Configure Wine), but without success too, this problem persist.

Trying your OS and wine version, I'm successful using the hints mentioned above. Unlike you, I can't get MP version working.


Settings to use native first, then builtin if it has problem...

If you use XP version of file, it might look ugly like this (when it works)...

[oops66]

OK, thanks for the information Marsh,
But strange !
You can not get XnViewMP-0.015 working on Wine 1.1.2, I can "almost perfectly"(version windows=win98 + Wine dll).
You can get XnView 1.94.2 working "almost perfectly"(without this kind of bug, windows=win2000 + native comctl32.dll), I can too but I have this bug.

So this topic is on stand-by.

[marsh]

( too many native comctrl32.dll version exist, I just need the good one - perhaps ?)

Here is a common reference available from the horse's mouth (same results)- I guess it shouldn't be needed, but ...

Platform SDK Comctl32 Redistributables 5.80.2614.3600 (x86)

http://www.microsoft.com/downloads/deta ... layLang=en

Look for: 50comupd.exe Open with 7zip (or any good archiver), extract comcnt.dll, rename it comctl32.dll and use.

[oops66]

Thanks for the link, but it's exactly the same version than I found via winetricks: http://wiki.winehq.org/winetricks

It doesn't matter, I will try some new tests later because, in fact, it's not a major bug.
So wait and see...
Thank you for all Marsh.