Hi Erik,
Did you make sure you have the "merge in the code" option checked ?
-----Message d'origine-----
From: Erik de Bruin
Sent: Friday, July 26, 2013 11:41 AM
To: dev@flex.apache.org
Subject: Re: [REQUEST] A tutorial on how to fix bugs for the Flex SDK
Ok, this is what I tried:
I created a new project in FB. It uses the 4.10 SDK in the FB/sdks
folder. In "project properties/Flex Build Path" on the "Source path"
tab I added the folder
"/Users/erik/Documents/ApacheFlex/git/flex-sdk/frameworks/projects/spark",
thinking this will allow me to work on the classic Spark components.
In my project, I add a Label in MXML. I cmd click on 'Label' to get me
into the Label source. I place a trace statement in the constructor. I
save, clean the project (just to be sure) and launch the project in
debug mode... No trace statement shows up :-( When I try to put a
breakpoint in the source, it complains there is no code on that line.
What am I doing wrong?
EdB
On Fri, Jul 26, 2013 at 1:38 AM, Alex Harui <aha...@adobe.com> wrote:
On 7/25/13 3:37 PM, "Justin Mclean" <jus...@classsoftware.com> wrote:
Hi,
but also means you don't have to build the SWCs before testing your
changes.
Perhaps I missing the point but if you make a change you will have to
recompile that project, you just don't have to recompile the entire SDK.
You are correct, but in my workflow, I don't even have to stop to compile
a single project.
For this resource module RTE I just worked on, I changed the files,
compiled the test case without running any ant scripts, and repeated until
it all worked. Then I go run a full build and start up mustella.
-Alex
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
