some parts cut out when sockreading

Print Thread

#16664 24/03/03 02:50 AM

GBX

i have a really weird prob
i do a normal sockread, only echoing der variable i read in and it returns the following:

Code:

&lt;td colspan="1" nowrap&gt;&lt;select class='mini' name='GameTypeSelect'&gt;&lt;option value="XGame.xBombingRun"&gt;Bombing Run&lt;/option&gt;&lt;option value="XGame.xCTFGame"&gt;Capture the Flag&lt;/option&gt;&lt;option value="XGame.xDeathMatch" selected&gt;DeathMatch&lt;/option&gt;&lt;option value="XGame.xDoubleDom"&gt;Double Domination&lt;/option&gt;&lt;option value="Excessive.ExcessiveBR"&gt;Excessive Bombing Run&lt;/option&gt;&lt;option value="Excessive.ExcessiveCTF"&gt;Excessive Capture The Flag&lt;/option&gt;&lt;option value="Excessive.ExcessiveDM"&gt;Excessive Death Match&lt;/option&gt;&lt;option value="Excessive.ExcessiveDD"&gt;Excessive Double Domination&lt;/option&gt;&lt;option value="Excessive.ExcessiveTDM"&gt;Excessive Team Death Match&lt;/option&gt;&lt;option value="SkaarjPack.Invasion"&gt;Invasion&lt;/option&gt;&lt;option value="BonusPack.xLastManStandingGame"&gt;Last Man Standing&lt;/option&gt;&lt;option value="BonusPack.xMutantGame"&gt;Mutant&lt;/option&gt;&lt;option value="Rocketeer084b.RocketeerGame"&gt;Rocketeer 2003&lt;/option&gt;[color:red]&lt;option value="XGame.xTe
thmatch&lt;/option&gt;[/color]&lt;/select&gt;

instead of:

Code:

... [color:red]&lt;option value="XGame.xTeamGame" selected&gt;Team Deathmatch&lt;/option&gt;[/color] ...

i examined the packages i received, but there was everything ok
so mirc cuts out some characters and put a $crlf instead
i really cant figure out why

Re: some parts cut out when sockreading #16665 24/03/03 03:48 AM
C codemastr
codemastr C	Did you remember that you must call sockread from within a loop? Meaning, a single sockread is not guaranteed to read all the data. Something like: (taken from the helpfile but modified to use local variables and a while() loop) Code: on 1:sockread:testing:{ var %temp if ($sockerr > 0) return while ($true) { sockread %temp if ($sockbr == 0) break if (%temp == $null) break echo %temp } }

Re: some parts cut out when sockreading #16666 24/03/03 09:36 AM
G GBX
GBX G	yes, i know, but i didnt want to post the whole html file the event is triggered several times before and after this line to be sure, i also tested your solution, but it didnt help it strongly seems to me that it is a mirc bug

Re: some parts cut out when sockreading #16667 24/03/03 12:09 PM
P ppslim
ppslim P	This is not a mIRC bug. mIRC is limited in the length it will store in a variable. As such, mIRC will fill it up, and as such, it wraps at the point where you claim the bug is produced. It is up to the script (you) to deal with search, replace, dis/asembly of the incoming text.

Re: some parts cut out when sockreading #16668 24/03/03 12:21 PM
G GBX
GBX G	i couldnt find a note describing a limitation on variables and this is not the first time this happened the last time the line was only about 10 chars long and if it is a limitation, how can i workaround it? what else can i do than letting sockread write into a variable? do i have to use a binvar which is really not very useful at this point?

Re: some parts cut out when sockreading #16669 24/03/03 12:26 PM
P ppslim
ppslim P	Parse the incoming text, and work out once the string is complete. Binvars will not help in any way, when reading this sort of text.

Re: some parts cut out when sockreading #16670 24/03/03 12:32 PM
G GBX
GBX G	ok, and where can i get the missing 25 characters?

Re: some parts cut out when sockreading #16671 24/03/03 02:58 PM
P ppslim
ppslim P	Use the "numbytes" parameter to limit the amount of bytes read from the socket EG, use 20 THis will prevent over-filling of variables.

Re: some parts cut out when sockreading #16672 24/03/03 04:35 PM
C codemastr
codemastr C	I would suggest you take a look at binary variables.

Re: some parts cut out when sockreading #16673 24/03/03 05:37 PM
G GBX
GBX G	numbytes only works with binvars i know how to use binvars, but that would be a very ugly solution

Re: some parts cut out when sockreading #16674 24/03/03 05:45 PM
C codemastr
codemastr C	You should really always use binvars when reading from a socket. So it wouldn't be an ugly solution, it would be a correct solution.

Re: some parts cut out when sockreading #16675 24/03/03 06:35 PM
G GBX
GBX G	correct solutions are only seldom the best solution ok, now i use binvars and it works, but the the size of the script is doubled and it is much more harder to read it not what i really wanted to but thx anyway seems to be really a limitation to string variables should be noted in the help file

Re: some parts cut out when sockreading #16676 24/03/03 08:10 PM
C codemastr
codemastr C	Ok then fine, come up with some other hack that will barely work and will provide confusion code. Me? Well I'd rather use correct well structured code that works in all circumstances. For example, mIRC strips a trailinf $crlf, well what if this were inside a tag say <textarea> where a $crlf is important? Using regular variables, your data is now invalid and corrupt, using binary variables it continues to work perfectly.

Re: some parts cut out when sockreading #16677 24/03/03 08:58 PM
G GBX
GBX G	i didnt say that vars are always better than binvars but in my case it is, because the code structure became worse btw the line doesnt contain a $crlf so the only problem was the string limitation i didnt know before same problem when reading over 4k data into a binvar, except that mirc cuts out some chars from the string but now it works, so thx to all for help

Re: some parts cut out when sockreading #16678 25/03/03 12:29 AM
C codemastr
codemastr C	But the 4k limit on binvars is not a hardlimit, you can easily change it using the "numbytes" parameter of sockread.

Re: some parts cut out when sockreading #16679 25/03/03 01:40 AM
K KiTiK
KiTiK K	I can say that this is not a long msg trouble. If the string is too long the script which echoes the string will be halted with this error msg: - * String too long: Somthing - It's not a bug, mirc returns what the net (or the socket) sends it! I hope I was clear, ZaC a.k.a. KiTiK

Re: some parts cut out when sockreading #16680 25/03/03 11:59 AM
G GBX
GBX G	this error msg occurs only if i sockread into a binvar und then copy the content to a string var but when you directly sockread into a var, no error msg comes up, only some chars missing, nothing else and i proved with a sniffer what exactly was sent to mirc i think the sockread command could be optimized to trigger an error msg if this happens or just dont cuts out chars anymore

Link Copied to Clipboard

Forums Bug Reports some parts cut out when sockreading