27 replies to this topic

[littlesat]

This is not the secondinfobar of the skin posted here!!! It could be that one of the pyo's in the package is making changes what we do not know....

Again..... forward your problem to the author of the skin!!!

Edited by littlesat, 5 April 2012 - 10:56.

[CoolST]

this secondinfobar im XT_image is - optional Secondinfobar .
it's not skin second infobar , it's the xt-image secound infobar and you can see it by every skin .

[veskop]

This is not the secondinfobar of the skin posted here!!! It could be that one of the pyo's in the package is making changes what we do not know....

Again..... forward your problem to the author of the skin!!!

OK,this is not second infobar,its extended info or whatever....anyway,its not present in your image...
it happened again,its not your fault the skin is OK,only with PLi image not work,so,where is the problem?in skin,or in image?I do not expect to answer me...

Edited by veskop, 5 April 2012 - 11:57.

[veskop]

This is not the secondinfobar of the skin posted here!!! It could be that one of the pyo's in the package is making changes what we do not know....

Again..... forward your problem to the author of the skin!!!

OK,this is not second infobar,its extended info or whatever....anyway,its not present in your image...
it happened again,its not your fault the skin is OK,only with PLi image not work,so,where is the problem?in skin,or in image?I do not expect to answer me...

thanks for a bad reputation littlesat... please,explain to other users,not to me,for what everytime when I ask "uncomfortable" questions,you give me bad reputation.Is v5 image based on your source code?why there this extended info is working?I can live without it,but it strange???I report gor a "bug",but you give me bad reputation!why?because you are boss here?OK,be happy,you are BIG strong guy here

Edited by veskop, 5 April 2012 - 12:14.

[littlesat]

You really do not understand it and I do respect your inquiries and conserns...

This skin is closed source.... But to fix it we have at least to know why!!! And even that is not possible..... That in the 2nd infobar of the skin the data looks different as on the printscreens is at least an indication that some pyo code is doing something we even can't know.....

I can only suggest that this skins designed most likely for an other image does expect the standard second infobar plugin and overrules that plugin something - something that is not possible because the second infobar is migrated into PLi... The skin.xml and the screendumps somehowe verifies my suggestions. And if so someone has to make the skin PLi-compatible... which only the creator of the skin could do.

The bad reputations is due to your replies......

Again.... as the skin has closed source python code we're not able to see the issue!!! So I already told you the solution... again forward it to the creator of the skin... he is the only one who could fix it... Pli-sources are open...!!

Edited by littlesat, 5 April 2012 - 12:18.

[littlesat]

Xqq double post...

Edited by littlesat, 5 April 2012 - 12:18.

[veskop]

The bad reputations is due to your replies......

I don't think with my reply's I had offended or affected someone, but this is your own decision.I just ask normal question...If skin doesnt work correctly in all PLi based images-OK,the skin is bad...But v5 is created with your sources,its a little bit strange?May be ,creators ot v5 images has change something?

[littlesat]

Do you know or have any idea what the V5 creators did change? It could be that they are based on PLi - but did not take/merge everything of our code....