我正在尝试学习BB10开发,所以我尝试下载他们的QNX Momentic IDE。
每当我运行应用程序时,它总会弹出一条消息“QML预览兼容性检查失败。禁用QML预览。”这显然是我的设计模式被禁用的原因。
我在网上搜索这个问题并发现类似的情况,我在网上发现的大多数情况大多与Java版本有关,所以我尝试了几个版本(1.6,1.7),我也试过我发现的线程中的解决方案这里QML Preview compatibility check failed. QML preview is disabled,但它仍然不起作用。所以尝试了另一个建议,看看C:\ Documents and Settings \ user \ ndk-10.1.0-workspace.metadata.log文件,看看是什么导致了这个问题,我发现我有不同的错误抛出我在网上找到的其他案例。
Here's the error:
!SESSION 2013-02-22 23:09:38.515 -----------------------------------------------
eclipse.buildId=10.1.0
java.version=1.6.0_24
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86
!ENTRY org.eclipse.ui 4 4 2013-02-22 23:09:42.781
!MESSAGE Plug-in 'com.rim.tad.tools.qml.javascript.debug.internal.ui' contributed an invalid Menu Extension (Group: 'jsdebug' is invalid): com.rim.tad.tools.wst.jsdt.debug.ui.jsunit.popup.evaluate
!ENTRY com.rim.tad.tools.qml.core 2 0 2013-02-22 23:09:43.234
!MESSAGE Cannot resolve ValueType variant: Number
!ENTRY com.rim.tad.tools.qml.core 2 0 2013-02-22 23:09:43.234
!MESSAGE Cannot resolve ValueType variant: QLocale
!ENTRY com.rim.tad.tools.qml.core 2 0 2013-02-22 23:09:43.234
!MESSAGE Cannot resolve ValueType variant: String
!ENTRY com.rim.tad.tools.qml.core 2 0 2013-02-22 23:09:43.250
!MESSAGE Cannot resolve ValueType variant: bb::device::CellularService::Types
!ENTRY com.rim.tad.tools.qml.core 2 0 2013-02-22 23:09:43.250
!MESSAGE Cannot resolve ValueType variant: Boolean
!ENTRY com.rim.tad.tools.qml.core 2 0 2013-02-22 23:09:43.250
!MESSAGE Cannot resolve ValueType variant: bb::system::SystemUiButton
!ENTRY com.rim.tad.tools.qml.core 2 0 2013-02-22 23:09:43.250
!MESSAGE Issues while loading Components Definition:
Duplicate Signal in: ComponentID: bb::cascades::InvokeActionItem, Signal: handlerChanged
!ENTRY com.rim.tad.tools.qml.simulator 1 0 2013-02-22 23:09:44.703
!MESSAGE C:\bbndk\ide\win32\x86\eclipse\jre\bin\java.exe -cp C:\bbndk\ide\win32\x86\eclipse\plugins\com.rim.tad.tools.qml.simulator_10.1.0.201302011933\ com.rim.tad.tools.qml.sim.check.RenderingCheck -target C:\bbndk\target_10_1_0_338\qnx6
!ENTRY com.rim.tad.tools.qml.simulator 4 0 2013-02-22 23:09:45.546
!MESSAGE QML Preview compatibility check log.
java.lang.IllegalStateException: glGetProcAddress_win32 failed: glGenFramebuffersEXT
at com.rim.tad.tools.qml.sim.CsApplicationEngine.nExec(Native Method)
at com.rim.tad.tools.qml.sim.CsApplicationEngine.execAndDestroy(CsApplicationEngine.java:45)
at com.rim.tad.tools.qml.sim.CsApplicationEngineThread.run(CsApplicationEngineThread.java:55)
Warning: WARNING: QApplication was not created in the main() thread.
Process exited with code: -1
!ENTRY org.eclipse.ui.workbench 2 0 2013-02-22 23:13:26.140
!MESSAGE A handler conflict occurred. This may disable some commands.
!SUBENTRY 1 org.eclipse.ui.workbench 2 0 2013-02-22 23:13:26.140
!MESSAGE Conflict for 'AUTOGEN:::org.eclipse.ui.cheatsheets.actionSet/org.eclipse.ui.cheatsheets.actions.CheatSheetHelpMenuAction':
HandlerActivation(commandId=AUTOGEN:::org.eclipse.ui.cheatsheets.actionSet/org.eclipse.ui.c heatsheets.actions.CheatSheetHelpMenuAction,
handler=ActionDelegateHandlerProxy(null,org.eclipse.ui.cheatsheets.CheatSheetExtensionFacto ry:helpMenuAction),
expression=AndExpression(ActionSetExpression(org.eclipse.ui.cheatsheets.actionSet,org.eclip se.ui.internal.WorkbenchWindow@2585e),WorkbenchWindowExpression(org.eclipse.ui.internal.Wor kbenchWindow@2585e)),sourcePriority=16640)
HandlerActivation(commandId=AUTOGEN:::org.eclipse.ui.cheatsheets.actionSet/org.eclipse.ui.c heatsheets.actions.CheatSheetHelpMenuAction,
handler=ActionDelegateHandlerProxy(null,org.eclipse.ui.cheatsheets.CheatSheetExtensionFacto ry:helpMenuAction),
expression=AndExpression(ActionSetExpression(org.eclipse.ui.cheatsheets.actionSet,org.eclip se.ui.internal.WorkbenchWindow@2585e),WorkbenchWindowExpression(org.eclipse.ui.internal.Wor kbenchWindow@2585e)),sourcePriority=16640)
现在,我不知道如何解决这个错误以及更多如何解决它。如果有人熟悉,如果你能投入一些意见或指出我正确的方向,我将不胜感激。
提前致谢。
答案 0 :(得分:1)
当我遇到此问题时,它一直是图形驱动程序的问题。您可能希望确保加载了最新的驱动程序。
答案 1 :(得分:0)
检查java版本,可能是你的JVM不支持-d32。