Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
RSPS style, except RSPS's usually do name.txt-based saving.I really cannot follow what RSPS is...
I recommend using BL_ID.txt-based saves.What? Thought I was the only one with that idea a year ago...
5000.txt
3: what else?Teaser: GUI
RP core has some general functionally issues and modifying it sucks because it has about 4 files that contain about 4 functions each, and there is little correlation to what is in each file.It is better to sort them into categorized files instead of having all mixed down in one file with 1000 rows that nobody want to scroll through.
RP Core was really good but I wasn't going to loving wait for real estate.I went into certain problems called "Schedule Quota Hit". I am going to fix the problem as soon as I'm done with some other things.
What files do you have at the moment? and do you have access to the etherpad?I just checked, and it seems that Etherpad is still online... yet...
I have absolutely no idea what point you're trying to make here. Why are you talking about AJAX and PHP?You said that you cannot send special characters with Torque. The same goes with AJAX. Therefor, if you convert the symbols to integers, you will get a really thought job to convert them back to characters in PHP.
FYI, AJAX has nothing to do with php.AJAX can only send UTF-8 characters, meaning that letters like åäö will crop the string from start to the first occurrence of those letters.
Since when? I think you need to revise character encoding.
PHP handles character encoding fine and Torque handles most character sets. I'm not sure what you're talking about.If you're using AJAX and sending characters not in the UTF-8 character encoding, it will split the string sent. If you instead turns the characters to integers before sending them, and then tries to return them back to the correct character on the server, PHP are only able to turn back UTF-8 characters.
Make it perfectly centered in 640x480 view, and then use horizSizing and vertSizing of "center"I didn't know that before I checked it up. That is the correct way of doing it.
No need to resize it manually, although that has its merits too.
We've just hit a roadblock in the buddy system. Basically the server only accepts UTF-8 character encoding and I'm pretty sure there are no character encoding functions in Torquescript so only people with non-handicapped characters in their names will be able to login.AJAX does also have this problem. the only thing to fix it is to put every character to an integer which represent each character, then convert them back to the original ones. The problem here is that PHP doesn't support those advanced characters and Torque obviously doesn't either...
I'm going to look at a number of methods to bypass this since I don't really want to have to put some string encoding utilities into v15 because that'd delay us substantially.
When did Badspot add a global list named $AddOnLoaded__?
