ID:135753
 Mar 4 2004, 6:18 pm
|
|
Could client.script be changed in a mob proc? Sorry about the brief post, but it's all I'm curious of. If you want an example, reply and I'll see if I can supply you(whoever wants to reply) with an example of what I mean.
| |
|
Mar 4 2004, 6:32 pm
|
|
Goku72
 |
I don't believe at this time there is. But, I believe that Lummox is pushing for this in recent upgrades...
|
Raven01 wrote:
Could client.script be changed in a mob proc? Sorry about the brief post, but it's all I'm curious of. If you want an example, reply and I'll see if I can supply you(whoever wants to reply) with an example of what I mean. I'm not sure yet if it's feasible to change scripts, and Tom insists that at the present time this is a bad idea, so it's been shelved. Considering all my effort to get margins to work right in 338 didn't even quite work out, I agree with him. Lummox JR | |
That's cool. I wanted to have a font that users could download and install to windows... And if they chose to install the font, they could switch between two different "scripts". One script would include a CSS element to use the font, and the other to use a default windows font (like Verdana)... That's what I was getting at.
| |
Raven01 wrote:
That's cool. I wanted to have a font that users could download and install to windows... And if they chose to install the font, they could switch between two different "scripts". One script would include a CSS element to use the font, and the other to use a default windows font (like Verdana)... That's what I was getting at. CSS already has support for that. It's a very intelligent format. See the following: body {color: #333300; background-color: #DDCC99; font-family: "Book Antiqua", "Times New Roman", serif; font-size: 12pt} This will use Book Antiqua if they have it. If they don't, it will fall back on Times New Roman. Assuming they don't have that either, it will use the first serif font on the system that it can find. | |