|
|
|
|
|
| Re: ADT problems [message #697733 is a reply to message #697646] |
Sun, 17 July 2011 22:11   |
|
On 2011.07.17 9:23, Angelo wrote:
> Hi thank you for the link it's of a good use but I suppose you can help
> me cause the problem is related to eclipse editor.
>
> I tested again and the problem happen inside the xml editor for the
> layout inside eclipse Helios or Indigo when I try to use quickdiff .
> While using quickdiff in java class files like main.R it works correctly
> replacing old code with the new suggestion without erasing other lines.
>
> It happened since upgrading to ADT 12 but strangely it continue to work
> fine inside Motodev 2.2.0
> Do I have to gave it up Indigo, and use Java perspective from Motodev?
> I have no idea what to do more after reinstalling eclipse and ADT 12.
>
> Thank you
> Angelo
You see, the Android development community has chosen to implement their
SDK atop Eclipse. They provide the plug-ins; Eclipse does not. It's not
impossible that there be a problem with Eclipse brought out by ADT, but
it's unlikely. There is, however, behavior that's Eclipse-influenced. I
just worked around it. (Try reading some of my article, written one year
ago).
You'll get a lot more sympathy and help in the Android forums because
that's where Android developers hang out.
Try these forums out. I did when I was doing Android and I got lots of
help from them.
When you ask your question, whether here or in an Android forum, try to
be very specific and think hard about what the reader would want to know
in order to answer.
|
|
|
| Re: ADT problems [message #697735 is a reply to message #697646] |
Sun, 17 July 2011 22:11 |
|
On 2011.07.17 9:23, Angelo wrote:
> Hi thank you for the link it's of a good use but I suppose you can help
> me cause the problem is related to eclipse editor.
>
> I tested again and the problem happen inside the xml editor for the
> layout inside eclipse Helios or Indigo when I try to use quickdiff .
> While using quickdiff in java class files like main.R it works correctly
> replacing old code with the new suggestion without erasing other lines.
>
> It happened since upgrading to ADT 12 but strangely it continue to work
> fine inside Motodev 2.2.0
> Do I have to gave it up Indigo, and use Java perspective from Motodev?
> I have no idea what to do more after reinstalling eclipse and ADT 12.
>
> Thank you
> Angelo
You see, the Android development community has chosen to implement their
SDK atop Eclipse. They provide the plug-ins; Eclipse does not. It's not
impossible that there be a problem with Eclipse brought out by ADT, but
it's unlikely. There is, however, behavior that's Eclipse-influenced. I
just worked around it. (Try reading some of my article, written one year
ago).
You'll get a lot more sympathy and help in the Android forums because
that's where Android developers hang out.
Try these forums out. I did when I was doing Android and I got lots of
help from them.
When you ask your question, whether here or in an Android forum, try to
be very specific and think hard about what the reader would want to know
in order to answer.
|
|
|
|
| Re: ADT problems [message #697996 is a reply to message #697845] |
Mon, 18 July 2011 14:50 |
|
On 18-Jul-11 01:55, Angelo wrote:
> Hi,
> Thank you again.
>
> I supposed was specific in my question and I'm not a proof developer.
>
> I find problems while changing the terms in the xml editor both when I use Eclipse or I run the java perspective from Motodev too. You can see from the screen shot attached.
>
> I suppose is a problem of the ADT because till I haven't made the update everything was working perfectly. When I stated that it worked inside Motodev was because I haven't updated motodev so, it had the old ADT in it's cache or similar I don't know how work such programs.
>
> If you have a work around please help me or indicate me a link to learn it. Attached you find 2 screen shots showing the problem I face.
> I run a windows xp professional sp3
>
> Thank you and regards
> Angelo
Content Assist is provided by Eclipse, but the content isn't the least
bit dependent upon it. While a picture is worth a thousand words and two
pictures two thousand, a description of what you think is the problem
would be even more worthwhile. From your images, I conclude nothing
except that the second one contains a bad attribute for a Gallery
definition.
|
|
|
|
| Re: ADT problems [message #698029 is a reply to message #698012] |
Mon, 18 July 2011 15:55 |
|
On 18-Jul-11 09:37, Angelo wrote:
> Hi,
>
> you don't see the problem? You don't see that in the second picture when
> I inserted the fill_parent the content assist erased the blank line and
> the rest of the code was written in the following line ?
> I haven't written it cause I already told you in the previous message
> what was happening. When I insert a new code frome the list this erase
> also the following digits present in the next lines.
> Pictures explain clearly it.
> Thank you to help me
Okay, I guess I see.
Does Android now claim to work with Indigo? I know that a year ago, it
claimed only to work with Galileo. I tried it with both Galileo and
Helios. I found both to work, but I haven't tried on Indigo yet. I'm not
an early adopter, I'm afraid.
In your case, it might be worth installing Helios and trying again. I
know that installing everything does take a little time, but it might be
worth it.
No, I've not had the trouble you show before.
Best of luck.
(I would still suggest stackOverflow because of the huge number of
developers there--one of whom just might know a work-around.)
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.09549 seconds
] 
Search
Help
Register
Login
Home
