Hi Charles,
Thanks for info on this. Unfortunately, I cannot reproduce this
problem, but here's what you can do:
If you visit ede-android-name-to-java, and put the cursor in the
function, then do:
M-x edebug-defun RET
it will enable debugging. You can then go back to your
AndroidManifest.xml, and use C-c . A to visit some activity, and it will
put a debug cursor in the function. Press SPC to advance, and see what
the outputs are. That should quickly inform you when some piece of data
is missing, and what may be going on.
To disable debugging, you can reload ede-android, or use C-M-x in
ede-android-name-to-java.
Thanks!
Eric
On 04/17/2012 12:03 PM, Charles Philip Chan wrote:
> Hello:
>
> I am starting to do some Android programming with the bzr trunk of
> cedet. Everything seems to be working with the exception of running the
> function "ede-android-visit-activity" on an activity in
> AndroidManifest.xml. Instead of finding the file in the correct path,
> the path is truncated. For example, if the package name is:
>
> org.foo.bar
>
> it will try to find the file in:
>
> src/org/
>
> instead of
>
> src/org/foo/bar/
>
> There seems to be a problem with "ede-android-name-to-java" which
> "ede-android-visit-activity" uses.
>
> Thanks.
>
> Charles
>
>
>
>
> ------------------------------------------------------------------------------
> Better than sec? Nothing is better than sec when it comes to
> monitoring Big Data applications. Try Boundary one-second
> resolution app monitoring today. Free.
> http://p.sf.net/sfu/Boundary-dev2dev
>
>
>
> _______________________________________________
> Cedet-devel mailing list
> Cedet-devel@...
> https://lists.sourceforge.net/lists/listinfo/cedet-devel
|