[p4] p4v 2007.3 and Qt "styles"

[Rick Macdonald]

I certainly will, but I'm hoping there's an environment variable or a 
setting in ~/.p4qt or elsewhere...

Rick

Stephen Vance wrote:
> Submit a bug/enhancement request to Support?
>
> Steve
>
> Rick Macdonald wrote:
>> I've just switch to the latest p4v, 2007.3. The default style is 
>> sickly pale looking to me. Too little contrast between widgets and 
>> frames, and the whole thing is light, bright, and hard on my eyes.
>>
>> The command line -style argument seems a bit flakey. Most styles, 
>> such as -style=sgi don't seem to do anything. In fact, other than 
>> "cde" and "motif", every other style looks the same. Even 
>> -style=foobar changes from the default to what you get with the other 
>> options such as -style=windows.
>>
>> Anyway, this is fine except when p4v launches the merge tool. It 
>> doesn't pass the style setting on the command line:
>>
>> rickm     6005  0.6  0.7  34288 15000 pts/4    S    10:02   0:00 
>> /home/rickm/SCM/GCTSCM/sccs2p4/tools/p4v-2007.3.151553/bin/p4v.bin 
>> -merge -nb //gct/batch/src/modules/xy2xy/v3.01/xy2xy.F#1 -nl 
>> //gct/batch/src/modules/xy2xy/v3.04/xy2xy.F#2 -nr 
>> /home/rickm/SCM/GCTSCM/sccs2p4/tools/cvs2p4/convdir-main/gct/batch/src/modules/xy2xy/xp/xy2xy.F 
>> -nm Merge file used for resolve -ll Source: -rl Target: -C none 
>> /tmp/rickm(p4v)/timshel_localhost_1666/gct/batch/src/modules/xy2xy/v3.01/xy2xy#1(BASE)[0].F 
>> /tmp/rickm(p4v)/timshel_localhost_1666/gct/batch/src/modules/xy2xy/v3.04/xy2xy(THEIR)[0].F 
>> /home/rickm/SCM/GCTSCM/sccs2p4/tools/cvs2p4/convdir-main/gct/batch/src/modules/xy2xy/xp/xy2xy.F 
>> /tmp/rickm(p4v)/timshel_localhost_1666/gct/batch/src/modules/xy2xy/v3.04/xy2xy(MERGE)[0].F 
>>
>>
>> I realize this is more of a Qt question, but does anybody know how to 
>> get a style setting to the merge tool when launched by p4v?
>>
>> Rick
>> _______________________________________________
>> perforce-user mailing list  -  perforce-user at perforce.com
>> http://maillist.perforce.com/mailman/listinfo/perforce-user
>>
>>   
>