Re: Debugging Wine with Lightroom 3.5

[Joris Huizer]

Replying, also including the wine-devel list,

On 12/17/2011 05:15 PM, Roland Baudin wrote:
> Hi,
>
> thanks for the answer.
> What do you mean by "a different execution path"?
> RB

The application might decide to execute different code given the Vista 
settings.
It may have a preferred execution path using certain functionality only 
available for Vista/Windows 7, and a fallback path for XP.

Pseudocode:
if (system is Vista+) use_builtin_functionality();
else /* XP */ use_fallback_mechanism();

HTH,
Joris

Debugging Wine with Lightroom 3.5

[Roland Baudin]

Yes, I suspected such a mechanism. Now if I understand well I have to 
find which one is the "builtin mechanism" and which one is the "fallback 
mechanism".
Is there some documentation around about the differences between Vista 
and XP?
Anyway, thanks for your help...
RB

Le 18/12/2011 13:40, Joris Huizer a écrit :
> Replying, also including the wine-devel list,
>
> On 12/17/2011 05:15 PM, Roland Baudin wrote:
> > Hi,
> >
> > thanks for the answer.
> > What do you mean by "a different execution path"?
> > RB
>
> The application might decide to execute different code given the Vista
> settings.
> It may have a preferred execution path using certain functionality only
> available for Vista/Windows 7, and a fallback path for XP.
>
> Pseudocode:
> if (system is Vista+) use_builtin_functionality();
> else /* XP */ use_fallback_mechanism();
>
> HTH,
> Joris

Debugging Wine with Lightroom 3.5

[Juan Lang]

Hi Roland,

On Sun, Dec 18, 2011 at 6:46 AM, Roland Baudin  wrote:
> Yes, I suspected such a mechanism. Now if I understand well I have to find
> which one is the "builtin mechanism" and which one is the "fallback
> mechanism".
> Is there some documentation around about the differences between Vista and
> XP?

That list would be large, too large to be conveniently listed in one
place.  What one could do, which is unfortunately often equally
tedious, is to compare +relay logs from running the app in Wine under
both modes.  If looking through multi-GB log files is your idea of
fun, you have the makings of a Wine developer ;)
--Juan

Debugging Wine with Lightroom 3.5

Yes, I'm that kind of person (I'm the developer of Xfe and TexMaths) but I've seen the +relay logs logs and they are indeed very huge, even for me!
RB

----- Mail original -----
De: "Juan Lang" 
À: "Roland Baudin" 
Cc: "Wine Devel" 
Envoyé: Dimanche 18 Décembre 2011 16:15:49
Objet: Re: Debugging Wine with Lightroom 3.5

Hi Roland,

On Sun, Dec 18, 2011 at 6:46 AM, Roland Baudin  wrote:
> Yes, I suspected such a mechanism. Now if I understand well I have to find
> which one is the "builtin mechanism" and which one is the "fallback
> mechanism".
> Is there some documentation around about the differences between Vista and
> XP?

That list would be large, too large to be conveniently listed in one
place.  What one could do, which is unfortunately often equally
tedious, is to compare +relay logs from running the app in Wine under
both modes.  If looking through multi-GB log files is your idea of
fun, you have the makings of a Wine developer ;)
--Juan

Debugging Wine with Lightroom 3.5

[Frédéric Delanoy]

On Tue, Dec 20, 2011 at 10:04,   wrote:
> Yes, I'm that kind of person (I'm the developer of Xfe and TexMaths) but I've seen the +relay logs logs and they are indeed very huge, even for me!
> RB

What you can do to reduce/manage the log size:
1. Launch any application (without logging), e.g. notepad, so the wine
startup doesn't produce (much) output
2. Run your app with the wine debugger to help with debug output control
http://www.winehq.org/docs/winedev-guide/dbg-commands#WINEDBG-DBG-CHAN
http://www.winehq.org/docs/winedev-guide/dbg-control

I think those links might help.

Frédéric

Debugging Wine with Lightroom 3.5

OK, thanks for your help.
I'll try this when I'll be back to home.
RB

----- Mail original -----
De: "Frédéric Delanoy" 
À: [e-mail]
Cc: "Juan Lang" , [e-mail]
Envoyé: Mardi 20 Décembre 2011 12:28:57
Objet: Re: Debugging Wine with Lightroom 3.5

On Tue, Dec 20, 2011 at 10:04,   wrote:
> Yes, I'm that kind of person (I'm the developer of Xfe and TexMaths) but I've seen the +relay logs logs and they are indeed very huge, even for me!
> RB

What you can do to reduce/manage the log size:
1. Launch any application (without logging), e.g. notepad, so the wine
startup doesn't produce (much) output
2. Run your app with the wine debugger to help with debug output control
http://www.winehq.org/docs/winedev-guide/dbg-commands#WINEDBG-DBG-CHAN
http://www.winehq.org/docs/winedev-guide/dbg-control

I think those links might help.

Frédéric

[SOLVED] Debugging Wine with Lightroom 3.5

[Roland Baudin]

Hi,

I finally solved the menubar issue (menubar not shown in Lightroom 3.x 
when Windows version is set to Windows XP or below).

I used a mix of the following patches :

- http://source.winehq.org/patches/data/67089 from Andrew Eikum 
(GetMenuBarInfo() partial implementation)

- http://www.winehq.org/pipermail/wine-patches/2006-April/026075.html 
from Thomas Kho (Fix GetMenuItemRect() for top-level menus)

You can find the attached complete patch against wine 1.3.35.

Have a nice day,
RB

Le 20/12/2011 12:28, Frédéric Delanoy a écrit :
> On Tue, Dec 20, 2011 at 10:04,  wrote:
> > Yes, I'm that kind of person (I'm the developer of Xfe and TexMaths) but I've seen the +relay logs logs and they are indeed very huge, even for me!
> > RB
>
> What you can do to reduce/manage the log size:
> - Launch any application (without logging), e.g. notepad, so the wine
>
> startup doesn't produce (much) output
> 2. Run your app with the wine debugger to help with debug output control
> http://www.winehq.org/docs/winedev-guide/dbg-commands#WINEDBG-DBG-CHAN
> http://www.winehq.org/docs/winedev-guide/dbg-control
>
> I think those links might help.
>
> Frédéric

[SOLVED] Debugging Wine with Lightroom 3.5

[Joris Huizer]

On 01/18/2012 10:10 PM, Roland Baudin wrote:
> You can find the attached complete patch against wine 1.3.35.

Hello Roland,

Please send patches to wine-patches.
Unless you are asking for feedback?

HTH,
Joris