Error opening editor (layout)

by arnouf » Sun, 14 Sep 2008 18:12:19 GMT


Sponsored Links
 ello all,

I'm trying to port my Ashopper project on 0.9...
I've a problem to use Android Layout editor. Apparently some of my
layout files are bad and when I try to launch the new tool Android
Layout editor, this is crashed. I get the following error:
"Error opening the editor". When i click on the "details" button I get
the following exception. FYI, I'm using eclipse 3.2. I can compile and
run my Android apps.
Thank you for your help.

java.lang.NullPointerException
at
org.eclipse.osgi.framework.internal.core.BundleLoader.getLoaderProxy(BundleLoader.java:
253)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.createExportPackageSource(BundleLoader.java:
225)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.getImportedSources(BundleLoader.java:
215)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findImportedSource(BundleLoader.java:
908)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findClassInternal(BundleLoader.java:
393)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:
369)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:
357)
at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:
83)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(Unknown Source)
at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.defineClass(DefaultClassLoader.java:
161)
at
org.eclipse.osgi.baseadaptor.loader.ClasspathManager.defineClass(ClasspathManager.java:
501)
at
org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findClassImpl(ClasspathManager.java:
471)
at
org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClassImpl(ClasspathManager.java:
430)
at
org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:
413)
at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:
189)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(BundleLoader.java:
340)
at
org.eclipse.osgi.framework.internal.core.SingleSourcePackage.loadClass(SingleSourcePackage.java:
37)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findClassInternal(BundleLoader.java:
405)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:
369)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:
357)
at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:
83)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
at java.lang.Class.getDeclaredConstructors0(Native Method)
at java.lang.Class.privateGetDeclaredConstructors(Unknown Source)
at java.lang.Class.getConstructor0(Unknown Source)
at java.lang.Class.newInstance0(Unknown Source)
at java.lang.Class.newInstance(Unknown Source)
at
org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrate



Error opening editor (layout)

by Xavier Ducrohet » Mon, 15 Sep 2008 00:37:23 GMT


 'm not 100% sure this is related, but the latest plugins require Eclipse 3.3

Xav

On Sun, Sep 14, 2008 at 3:12 AM, arnouf <[EMAIL PROTECTED]> wrote:

--~--~---------~--~----~------------~-------~--~----~


Sponsored Links


Error opening editor (layout)

by arnouf » Mon, 15 Sep 2008 01:24:56 GMT


 ooo!! I upgraded my Eclipse installation from 3.3 to 3.2 because I
saw on installation guide that 3.2 was required...It should be 3.3???

Hummm...I'll try this later and I come back to give a summarize !

Regards

On 14 sep, 18:37, "Xavier Ducrohet" <[EMAIL PROTECTED]> wrote:
--~--~---------~--~----~------------~-------~--~----~



Error opening editor (layout)

by Xavier Ducrohet » Mon, 15 Sep 2008 05:13:39 GMT


 revious plugins required 3.2 minimum. The new plugins that go with
the 0.9 SDK require 3.3 minimum.

Xav

On Sun, Sep 14, 2008 at 10:24 AM, arnouf <[EMAIL PROTECTED]> wrote:

--~--~---------~--~----~------------~-------~--~----~



Other Threads

1. ListView/ ScrollView : What exactly is happening in onInterceptTouchEvent()

I know that we are not supposed to put a listView inside of a
scrollView.  The layout  and nesting of my apps views are determined
at run time and I have no control over that.My situation demands it
and I have a working implementation to achieve that.  However I am not
sure what exactly is happening in  onInterceptTouchEvent().

I am returning false from onTouchEvent() ,of scrollView, if the
MotionEvent occurred within the bounds of the listView, thus the event
is passed down to my listView to handle. So if I touch and drag
outside the listView my outer scrollView scrolls, else if I touch and
drag on the listView, the listView scrolls. They dont compete for
scrolling anymore. This is all possible only if I always return false
from the  onInterceptTouchEvent() of the scrollView. In the default
implementation it returns true if it is being dragged. My solution
breaks if I return true from here for any condition. Is it ok to
simply return false all the time from  onInterceptTouchEvent()? I have
tried scrolling in several ways and both the scrollview and the
listView are scrolling as expected when I return false.

A standalone listView also works fine when I simply return false from
its onInterceptTouchEvent() instead of  returning  super(AbsListView).
onInterceptTouchEvent()

Anyone has any scenario when the scrolling might not work?

thanks,
vk

-- 

2. Weird Camera Intent behavior

Hi all.

I'm invoking the MediaStore.ACTION_IMAGE_CAPTURE intent with the
MediaStore.EXTRA_OUTPUT extra so that it does save the image to that
file.



On the onActivityResult I can check that the image is being saved in
the intended file, which is correct. The weird thing is that anyhow,
the image is also saved in a file named something like
"/sdcard/Pictures/Camera/1298041488657.jpg" (epoch time in which the
image was taken).

 I've checked the Camera app source (froyo-release branch) and I'm
*almost* sure that the code path is correct and wouldn't have to save
the image, but I'm a noob and I'm not completly sure. AFAIK, the image
saving process starts with this callback (comments are mine):

private final class JpegPictureCallback implements PictureCallback {
...
    public void onPictureTaken(...){
        ...
        // This is where the image is passed back to the invoking activity.
        mImageCapture.storeImage(jpegData, camera, mLocation);
        ...

        public void storeImage(final byte[] data,
                android.hardware.Camera camera, Location loc) {
            if (!mIsImageCaptureIntent) {      // Am i an intent?
                int degree = storeImage(data, loc); // THIS SHOULD NOT
BE CALLED WITHIN THE CAPTURE INTENT!!
             .......

       // An finally:
        private int storeImage(byte[] data, Location loc) {
            try {
                long dateTaken = System.currentTimeMillis();
                String title = createName(dateTaken);
                String filename = title + ".jpg";  // Eureka,
timestamp filename!
                 ...

So, I'm receiving the correct data, but it's also being saved in the
"storeImage(data, loc);" method call, which should not be called...


It'd not be a problem if I could get the newly created filename from
the intent result data, but I can't. When I found this out, I found
about 20 image files from my tests that I didn't know were on my
sdcard :)

I'm getting this behavior both with my Nexus One with Froyo and my
Huawei U8110 with Eclair.

Could please anyone enlight me? Dianne? ;)

Thanks a lot.

-- 

3. Which is the best way to implement double buffering?

4. Spaces in links to Android Developers reference

5. Problem with WebView

6. Honeycomb SDK

7. Does Android have a LinkButton. Basically like text but you click on it?