<div>Hi Daniel,</div>
<div> </div>
<div>I'm using the build of 4.6beta3 for windows that was made available for download from <a href="http://maptools.org">maptools.org</a> today.</div>
<div> </div>
<div>If TRANSPARENT is within the outputformat, mapserver fails and returns the following error message:</div>
<div> </div>
<div>"GD/JPEG OUTPUTFORMAT jpeg has TRANSPARENT set ON, but this is not supported. It has been disabled."</div>
<div> </div>
<div>Leaving TRANSPARENT out of the outputformat block prevents the error message, and the map appears to be generating properly including transparancy. Previously I had to have TRANSPARENT ON in my outputformat block to enable transparancy.
</div>
<div> </div>
<div>If this was the intended effect, then just the 4.6 documentation needs to be updated for the syntax change. I brought this up because the change was not listed in the revision history in history.txt, and the mapserver log and our flash interface don't show this error message, leaving me to try it out in an HTML template when our flash site failed.
</div>
<div> </div>
<div>Thanks again,</div>
<div>Ken </div>
<div> </div>
<div><br><br> </div>
<div><span class="gmail_quote">On 5/31/05, <b class="gmail_sendername">Daniel Morissette</b> <<a href="mailto:dmorissette@dmsolutions.ca">dmorissette@dmsolutions.ca</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Ken Lord wrote:<br>> I don't know if this is a bug or a feature, but the move from 4.6beta2<br>> to
4.6beta3 has disabled the use of the parameter "TRANSPARENT ON/OFF"<br>> within OUTPUTFORMAT.<br>><br><br>Well, setting TRANSPARENT ON/OFF (or TRUE/FALSE) in an OUTPUTFORMAT<br>block in the mapfile works for me with
4.6beta3, and the resulting image<br>has the right transparency (I used GIF for my tests).<br><br>What happens or doesn't happen exactly for you? Is it that you get a<br>mapfile parsing error, or simply that transparency appears to not be
<br>working but you get no error message? Are you sure it's not something<br>else that changes in your test environment (or a broken build)? Perhaps<br>you could file a bug if you are able to include a simple testcase to<br>
reproduce.<br><br>Daniel<br>--<br>------------------------------------------------------------<br>Daniel Morissette <a href="mailto:dmorissette@dmsolutions.ca">dmorissette@dmsolutions.ca</a><br>DM Solutions Group
<a href="http://www.dmsolutions.ca/">http://www.dmsolutions.ca/</a><br>------------------------------------------------------------<br></blockquote></div><br>