locked
SettingsPane::GetForCurrentView() causing COMException

    Question

  • I get this additional information from the exceptions:

    HRESULT:0x80070490 Element not found.
    WinRT information: Call to IFrameworkView::Initialize failed

    This is in a Metro Direct3D project, inside:

    void MyApp::Initialize(CoreApplicationView^ applicationView)

    Since it's D3D, I'm not using XAML. Is that required to add settings charms?

    Software Engineer, Brainium Studios LLC

    Monday, April 30, 2012 10:58 PM

Answers

  • I was using it in :

    void MyApp::Initialize(CoreApplicationView^ applicationView)

    which, I'm guessing, is too early. I moved it to:

    void MyApp::SetWindow(CoreWindow^ window)

    and now it's fine.


    Software Engineer, Brainium Studios LLC


    Tuesday, May 1, 2012 5:19 PM

All replies

  • Hello,

    Would you please provide us more codes to reproduce this issue?

    Or you can upload your project to
    http://skydrive.live.com/

    It is not necessary that you send out the whole of your project. We just need a simplest sample to reproduce the problem. You can remove any confidential information or business details from it.

    Best regards,
    Jesse


    Jesse Jiang [MSFT]
    MSDN Community Support | Feedback to us

    Tuesday, May 1, 2012 5:53 AM
  • I was using it in :

    void MyApp::Initialize(CoreApplicationView^ applicationView)

    which, I'm guessing, is too early. I moved it to:

    void MyApp::SetWindow(CoreWindow^ window)

    and now it's fine.


    Software Engineer, Brainium Studios LLC


    Tuesday, May 1, 2012 5:19 PM
  • I had this occur also when I put the SettingsPane.GetForCurrentView() too early in my App.xaml.cs (C# app). I moved it inside the OnLaunched handler and it worked.

    Just noting this in case anyone got the same error in a C#/XAML app.


    Jay in Atlanta

    Friday, February 1, 2013 10:58 PM