no trace output and breakpoints not taken in flashdevelop

[Doug Snyder]

i have created a haxe->js project in flashdevelop.  i added a trace( "hello" ) statement in main(), but i get no text output and a breakpoint on that statement never happens.

i have selected a debug configuration and i have set the "enable debugger" to true in the compiler option properties.

does anyone know what i am missing, here?

thanks,

doug

[Philippe Elsass]

JS trace/debug has to be done in the browser (FD only debugs Flash) - using Chrome you can enable Source Mapping (search for it) to debug Haxe code directly and set breakpoints.

--
To post to this group haxe...@googlegroups.com
http://groups.google.com/group/haxelang?hl=en
---
You received this message because you are subscribed to the Google Groups "Haxe" group.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
Philippe

[Doug Snyder]

i turned on the developer tools and enabled source mapping, but the mapping to haxe doesn't seem to be working - i see the .js code, not the .hx code

what are the correct steps for starting a debug session from flashdevelop?

thanks,

doug

[david quertelet]

you have to add -debug in  your compilation settings ..

and check the source tab in chrome ...

[Doug Snyder]

my compile settings are 

    "haxe -cp src -js C:/Doug/Projects/DTO/DTO_Haxe/bin/DTOHaxe.js -main Main -debug"

what do mean by: " check the source tab in chrome ..."?  the chrome browser has no source tab and the developer tools has a "Sources" tab near the top of the window, but it can't be checked.

thanks,

doug

Re: [haxe] Re: no trace output and breakpoints not taken in flashdevelop

you have to add -debug in  your compilation settings ..

and check the source tab in chrome ...

Le mardi 2 avril 2013 à 17:32, Doug Snyder a écrit :

On Monday, April 1, 2013 10:48:49 PM UTC-7, Doug Snyder wrote:

[Raoul Duke]

i think the developer tools might have changed look and feel depending
on what version of chrome/chromium is used, over the years. the basic
idea is, yes, look for "developer tools" then look for "scripts" and
see what is in there. sometimes there is a drop-down menu for picking
the source .js file, if you are in a situation with more than one.
also sometimes i think some of the tabs in older chrome developer
tools would be disabled / turned off by default, you had to enable
them?

[david quertelet]

yeah that's right " the sources tab" when you inspect element... 

your compile settings are fine ! 

it should work! 

[Greg Dove]

You should see another file DTOHaxe.js.map generated alongside DTOHaxe.js in the bin directory. 

Greg Dove
Dove Software Development Ltd
http://greg-dove.com

[Greg Dove]

I don't think I had to switch on 'enable source mapping' although maybe I did and can't remember it. Instructions here - about the cog icon/button in lower right of developer tools:

http://haxe.org/doc/js/source_debugging

Greg Dove
Dove Software Development Ltd
http://greg-dove.com