Quote:
Originally Posted by Muddy_Waters
Wow, I must say I'm really not that used to first posts that are as comprehensible as yours. :)
|
Thank you for some good word, tried to keep my 'problems' organized and understandable.
2nd issue - No Colors
-----------
Quote:
Originally Posted by Muddy_Waters
Since the first issue has already been resolved, let's get straight to the second issue:
And to be quite frank, I don't really have a clue of how to fix this one. Though I don't assume this to be an issue that is related to my version exclusively, as the problem also persists when viewing an xml itemlog using Firefox. Are you using a Polish Version of Windows as well?
|
No, i am using using original english language windows 7 x86 sp1 ult. Yes indeed, using firefox colors are also affected just the same as in opera.
Quote:
Originally Posted by Muddy_Waters
This is just a wild guess, but I could imagine this to be related to your windows character set - but again, this is merely a hunch, after all I'm not a professional. :o
|
Here is what i did and got *some* effect. I copied folder
<mycharname> with all the files in it to some other location. Edited *.xml and *.xsl files:
Quote:
*.xml line 1: from <?xml version="1.0" encoding="iso-8859-1"?> to <?xml version="1.0" encoding="iso-8859-2"?>
*.xsl line 1: from <?xml version="1.0" encoding="iso-8859-1"?> to <?xml version="1.0" encoding="iso-8859-2"?>
and line 3: from <xsl:output method="html" encoding="iso-8859-1" doctype-system="http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd" doctype-public="-//W3C//DTD XHTML 1.1//EN"/> to <xsl:output method="html" encoding="iso-8859-2" doctype-system="http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd" doctype-public="-//W3C//DTD XHTML 1.1//EN"/
|
those three changes resulted in such a nice change:
Quote:
i have 'language for non-unicode programs: polish' set, seeing this is a encoding issue i changed this setting to 'language for non-unicode programs: united kingdom'.
This has resolved the color issue! however, i am afraid i will have to jugle this non-unicode setting while installing some software. is there no way i can get colors output right with my native language as one for non-unicode programs?
maybe it is a suggestions for future release, to make this ingenious invention of yours more compatibile with system language settings?
Quote:
Originally Posted by Muddy_Waters
However, the color of the terms in itemlog can be changed relatively easily as I merged all manager itemlog outputs into one single function, called MWI_WriteManagerLog(). As the prefix already indicates, this function is defined in the MWItemlogger library.
To alter the colors, just add the appropriate color codes at the very front of the strings that are being assigned in the first switch statement in the function mentioned above.
|
Since i didnt understang much of that last sentence i used logic and some basic html/css/programming knowledge i have. i edited this spot:
Quote:
|
Originally Posted by MWItemlogger.ntl
switch(mode)
{
case 0: // Kept
_output += "Kept ";
break;
case 1: // Gambled
_output += "Gambled ";
break;
case 2: // Cubed
_output += "Cubed ";
break;
case 3: // Sold
_output += "Sold ";
break;
}
|
So it seems to be working, and from now on 'kept' are 'set green' "ÿc2Kept " for example and 'sold' are red "ÿc1Sold ". I changed all the cases 0 -> 3 to my liking. Thank you very much for this tip!
In general I would like to have what we have acomplished here used. Maybe a partioal sticky? i would like to share our/my solution regarding d2nt color issues. Posting all this while fixing alone, took me many hours so lets help out some other 'evil botters' :P
whaddya say? it would be a shame to waste all effort put into this.
for example here you reffered to the color issue:
Quote:
Originally Posted by Muddy_Waters
For some reason, the color codes within the output strings are not converted into actual colors correctly.
I'm not quite sure what causes this error as I can't remember anyone having the same problem.
Try disabling visual design and desktop compositions, though I'm not sure if this will help.
|
now it is somewhat resolved.
3rd issue - Logs
-----------
Quote:
Originally Posted by Muddy_Waters
Regarding your third issue:
Activating the nip debug mode will extend the item tooltips for items in the manager's itemlog and applies only for those items that are being kept.
You cannot show nip lines for items that are not being kept, because the absence of such a line is the very reason the item is not kept in the first place. ;)
|
of course... my bad, now i'm ashamed a little for my foolishness. in that case i will ask a little different matter.
how to print out to *.xml file this nip debug? so that i could review more detailed causes of my items kept in the past.
*NEW 4th issue - Restarts*
------------
after a night of bot runs i managed to gather such a statistics:
Runs: ~70 ; Restarts: ~7
this gives about 10% fail ratio which compared to my previous, d2nt 3.0 bot's <1%, is a bit high.
Big question: are there any common resasons? what may be the reason?
Finishing question: do you plan on expanding xml log options? for example mentioned nip debug info? or advanced filter/sorting options: time, found at, item class/type (big classes: aromor, weapon, charm, to-socket etc. ; detailed class: helm, armor, gloves, boots, small charm, runes etc ; type: unique, set, runeword, rare, magic, normal, sockets, ethereal ; rarity: normal, exceptinal, elite)? or outputting to *.xml gamble and game statistics?
Imho it would be a very nice perk and a useful tool.
Thank you very much for pointing me the right direction to look for an answer, your help was priceless especially with kept/sold color! apart from this 10% crash ratio everything works like a (perfect anni :p ) charm hehe.
Important Edit:
out of curiosity I checked if it will now output colors and fonts properly with polish version. And it does! unfortunately it still crashes on some items... now it crashed 2 times while trying to log 'Dangoon's Teaching'. However it is a good start to make it work on other languages :)