Debugging tools

[Jim O'Leary]

It may be "correct behavior", but how do I find out why the points don't show
up on my map? The only way is to descend into the code to the level of a
core developer. As I said, most developers will not have the time or
inclination to make that commitment. They just want to use the API.


Traian Stanev wrote:
> 
> 
> 
> In this case error logging would not have helped, since there is not
> really an error. If a layer has no PointTypeStyle, point geometries will
> not draw and this is correct behavior. You must have a style in order
> for geometries to draw. This effectively gives you a way to filter out
> geometry types from a layer with mixed geometries. 
> 
> 
> 
> Traian
>  
> 
> -----Original Message-----
> From: Bruce Dechant 
> Sent: Thursday, September 07, 2006 4:25 PM
> To: users at mapguide.osgeo.org
> Subject: RE: [mapguide-users] RE: Debugging tools
> 
> The server currently does not log any errors to the server error log if
> a layer fails to stylize for any reason. This is a confirmed bug and
> will be fixed for the Tux SP1. 
> 
> Bruce
> 
> -----Original Message-----
> From: Dave Wilson
> Sent: September 7, 2006 1:18 PM
> To: users at mapguide.osgeo.org
> Subject: RE: [mapguide-users] RE: Debugging tools
> 
> It seems that what your are seeing is not a framework/coding debug issue
> rather a bug in the code where it fails to generate an exception.
> 
> This needs to be logged as an artifact if that is the case.
> 
> Regards,
> Dave
> 
> -----Original Message-----
> From: Jim O'Leary [mailto:joleary.public at gmail.com]
> Sent: Thursday, September 07, 2006 10:58 AM
> To: users at mapguide.osgeo.org
> Subject: [mapguide-users] RE: Debugging tools
> 
> 
> Yes, I have error reporting turned on. Actually you can do this without
> touching php.ini. Just create a file called, say, "ini_set.php" and put
> the following code in it:
> 
>   // E_ALL is 8191, E_NOTICE is 8.
>   // See
> http://ca.php.net/manual/en/ref.errorfunc.php#errorfunc.constants
>   ini_set("display_errors","On");
>   $error_reporting =8191 & ~8;
>   ini_set("error_reporting",$error_reporting);
> 
> Then reference it in each PHP program that you want errors to display:
> 
> include "../ini_set.php";
> 
> My point, however, is that MagGuide, either through PHP or through some
> other exception, did not generate an error at all. It would have been
> helpful to get an error message, like,
> 
> "You are trying to add a point to a batch property collection, but you
> don't have a point definition in your layer definition schema".
>        
> 
>    
> Jason Birch wrote:
>> 
>> So there was a PHP error that was not returning?
>> 
>> I believe that the php.ini file that ships with MapGuide has error 
>> reporting turned off.  If you turn it on, maybe you would get what you
> 
>> need in your case?
>> 
>> Jason
>> 
>> -----Original Message-----
>> From: Jim O'Leary [mailto:joleary.public at gmail.com]
>> Sent: Thursday, September 07, 2006 08:21
>> To: users at mapguide.osgeo.org
>> Subject: [mapguide-users] Debugging tools
>> 
>> 
>> Are there any debugging tools for MapGuide OS? When I add an 
>> enhancement to an existing sample, the enhancement does not appear but
> 
>> there is no indication from the application where the problem lies.
>> 
>> For example, recently I set out to add point redlining to the line 
>> redlining sample, draw_line.php, modifying the code from 
>> create_new_point_layer_definition.php and adding it to draw_line.php.
>> However, the map continued to redline the lines, but not the points, 
>> with no debug messages.
>> 
>> I got deep into the code and realized I had to add a PointTypeStyle 
>> section to the layerDefinition. I could find nothing in the 
>> documentation or in the output of the program to indicate that this 
>> was the problem. It took me several hours to do this.
>> 
>> I think that developers who want to use the MapGuide APIs should not 
>> have to get into the code at the level of a core developer in order to
> 
>> use it. I suspect that many would not have the time to do that. A 
>> debugging tool would be most helpful.
>> --
>> View this message in context:
>> http://www.nabble.com/Debugging-tools-tf2233805.html#a6192404
>> Sent from the OSGeo MapGuide forum at Nabble.com.
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe at mapguide.osgeo.org
>> For additional commands, e-mail: users-help at mapguide.osgeo.org
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe at mapguide.osgeo.org
>> For additional commands, e-mail: users-help at mapguide.osgeo.org
>> 
>> 
>> 
> 
> --
> View this message in context:
> http://www.nabble.com/Debugging-tools-tf2233805.html#a6194262
> Sent from the OSGeo MapGuide forum at Nabble.com.
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe at mapguide.osgeo.org
> For additional commands, e-mail: users-help at mapguide.osgeo.org
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe at mapguide.osgeo.org
> For additional commands, e-mail: users-help at mapguide.osgeo.org
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe at mapguide.osgeo.org
> For additional commands, e-mail: users-help at mapguide.osgeo.org
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe at mapguide.osgeo.org
> For additional commands, e-mail: users-help at mapguide.osgeo.org
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Debugging-tools-tf2233805.html#a6208881
Sent from the OSGeo MapGuide forum at Nabble.com.