I'm going around in circles here… I have two problems. One with playerglobal.swc and another with textLayout.swc
1) When I link the develop SDK to a project, I get two swc links: playerglobal.swc and "11.1". It can't find either of those. I can manage to get the SDK to work by unlinking those and linking to a valid copy of playerglobal on my machine. This is workable, but I'm concerned by why I need to do that. It's also a pain to do this every time I want to use the dev sdk… 2) textLayout.swc works, but I does not get linked to source. When I try to jump to the source of any TLF classes I get an error that the source cannot be found. I tried linking to textLayout.swc in the tlf folder instead and I have the same problem. I'm able to recompile and test my changes, but I can't do any real debugging if it does not link to the source… Any ideas on how I can fix this? Harbs On Sep 2, 2013, at 8:30 AM, Alex Harui wrote: > > > On 9/1/13 10:21 PM, "Harbs" <harbs.li...@gmail.com> wrote: > >> Okay. Makes sense. >> >> And how do you set breakpoints in the code? > I'm not using FB. FDB allows me to set breakpoints just fine. FB should > too given that it will use the path in the SWC that you built on your > machine so it should be an exact match. >> >> Does it make sense to include the swcs in the TLF folder instead of the >> ones in the sdk folder? > The build script in flex-sdk/frameworks/projects/textLayout should copy > the SWCs from wherever flex-tlf puts it. > > -Alex >
