Changes between Initial Version and Version 2 of Ticket #2623


Ignore:
Timestamp:
May 21, 2008, 5:25:25 AM (16 years ago)
Author:
dmorissette
Comment:

The _map_handle_ approach could possibly work, but the handle of the PHP object at map->outputformat would be invalid (since it would still refer to the original outputFormatObj C struct).

Perhaps a cleaner fix would be to destroy the map->outputformat PHP object (which is a PHP wrapper with a ref to the C struct with a stub destructor that does nothing) and create a new one in php3_ms_map_selectOutputFormat() using _phpms_build_outputformat_object()? I don't think we do that kind of stuff anywhere yet, but this way the handle would be maintained properly.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #2623

    • Property Milestone5.2 release
  • Ticket #2623 – Description

    initial v2  
    11Here is a scenario:
    22
    3 mapfile contains and imagetype and one out
     3mapfile contains an imagetype and one outputformat
    44
     5{{{
    56  IMAGETYPE png
    67
     
    1011    ...
    1112  END 
    12  
     13}}}
     14
    1315 php script
    1416
    15   $map_file="f:/msapps/gmap_pdf/htdocs/gmap75.map";
     17{{{
     18$map_file="f:/msapps/gmap_pdf/htdocs/gmap75.map";
    1619$oMap = ms_newMapObj("$map_file");
    1720$oMap->selectOutputFormat("mypdf");
    1821$oMap->outputformat->setOption("aaa", 30);
     22}}}
    1923 
    2024 This has the effect of modifying the "wrong" outputformat (in this case the outputformat defined as "png") instead of modifying the "mypdf" format.
    21