<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<small>Thanks Daniel,<br>
<br>
That explains things! Exactly the explanation my colleague suggested.<br>
<br>
Cheers<br>
Matthew</small><br>
<br>
Daniel Morissette wrote:
<blockquote cite="mid4254B2B3.4060506@dmsolutions.ca" type="cite">Camden
Daily wrote:
<br>
<blockquote type="cite">It seems that many of the member values of
mapscript objects are not
<br>
directly accessible. They are only available to be set with the set()
<br>
function. I do not know if this is a bug or a design decision, but it
<br>
would certainly be nice to make those variables all public.
<br>
<br>
</blockquote>
<br>
You need to use the set() methods to set any member variables in PHP
<br>
MapScript objects. This is because PHP MapScript objects are just PHP
<br>
wrappers on top of the MapServer C structures, and when you set the
<br>
variables explicitly using $point->x=1; then the value in the PHP
<br>
wrapper is set, but the value is not propagated to the lower-level
<br>
object inside MapServer because there was no way in PHP 4 to trap a
<br>
change to an object member variable.
<br>
<br>
In PHP5 this has been fixed, it will be possible to have callbacks
<br>
(internally) to catch the change to the member variables and we'll be
<br>
able to get rid of the set() methods... but this has not been
<br>
implemented yet for PHP MapScript.
<br>
<br>
Daniel
<br>
--
<br>
------------------------------------------------------------
<br>
Daniel Morissette <a class="moz-txt-link-abbreviated" href="mailto:dmorissette@dmsolutions.ca">dmorissette@dmsolutions.ca</a>
<br>
DM Solutions Group <a class="moz-txt-link-freetext" href="http://www.dmsolutions.ca/">http://www.dmsolutions.ca/</a>
<br>
------------------------------------------------------------
<br>
<br>
</blockquote>
</body>
</html>