Momentics qml full fon

How can I change the size of the font of the qml Editor?

I figured it finally:

QML-> General-> appearance-> Basic-> text fonts

JavaScript-> General-> aspect-> JavaScript-> text JavaScript Editor fonts

C / C++-> General-> aspect-> C / C++-> Edior-> C/C++ editor text fonts

No shortcuts!

Very convinient

Tags: BlackBerry Developers

Similar Questions

I'm running a full scan of the system with my anti-virus software and it filled almost my laptop crashes, problem with the vga865.fon file

I'm running a full scan of the system with my anti-virus software and it filled almost my laptop breaks down when it comes to: -.

c:\windows\winsxs\x86_microsoft-Windows-font-bitmap-oem_31bf3856ad364e35_6.0.6000.16386_none_fb2d5aefb17b8d65\vga865.FON

This file can be replaced. When I scan this folder individually its fine, please help

Thank you

Hello

What protection software antivirus you are running on the computer?

Method 1: Check if you can run the scan in safe mode without in all questions

Follow the steps mentioned in the link below to access the secure mode
Startup options (including safe mode)

Method 2: you can run Safe Mode security monitor, see the steps in the article below
How to install the free Windows Live OneCare Safety Scanner and then scan your computer in Mode safe

Method 3: Follow the steps mentioned in the link below to check your hard disk for errors, and then check if the problem is resolved
Check your hard drive for errors

If the problem persists,

Method 4: Long file name could cause this problem, perform a backup of the file (copy it somewhere else), and then rename the file, check to see if that makes a difference

Note: Copy the file to the original location.

Thank you, and in what concerns:

Ajay K

Microsoft Answers Support Engineer
***************************************************************************
Visit our Microsoft answers feedback Forum and let us know what you think.

How to open cordova 6 blackberry10 project in Momentics IDE

I am new to develop 10 Blackberry Cordova

How open created Cordova balckberry10 native Momentics IDE project

Even now, I see no pages or videos as cordova andriod

Please help me if you know links.

BlackBerry Momentics does not support HTML5 or Cordova development. It can be used to develop applications using C/C++ and QML Qt or stunts. It is not an IDE for creating HTML content.

You can use it to create a native extension for use in application of Cordova, but I don't think that's what you're looking for here.

HOWTO: Translation Live in C++ similar to re-translate in QML

WARNING: To come long post!

If you've built (or building) your apps BlackBerry 10 Aboriginal stunts with internationalization in mind, then you have probably dotted with QML qsTr() calls and macros tr() C++ code. When your application starts the text wrapped in qsTr() or tr() is replaced by the localized text for the local unit and the language (if defined, otherwise default text is used). This works fine unless you change the language setting on your device while your application is running. Unless you take measures to propagate the change to the language through your live webcam app, the text displayed in your application will not match the settting of language new device only when your application is restarted. QML provides this translation of 'direct' with the re-translation class, which can be used with qsTr() update of translations that soon the language setting of the device is changed:
```
Page {   Container {      Label {         id: label01

         // ---This label's text will be live translated         text: qsTr("Label 1") + Retranslate.onLanguageChanged      }      Label {         id: label02

         // ---This label's text will be static translated         text: qsTr("Label 2")      }   }}
```
In this example, label01 will be his attribute of translated text live as it is updated as soon as the device language is changed. However, label02 will have only his attribute of text translated when the software is first started and the language changes following while the application is running will not update to it.

With the help of the re-translation with QML class makes direct translation as simple as the addition of a small amount of code just after each use of qsTr(), but C++ does provide no such convenience. To implement the translation directly in C++ code, it is necessary to call setXXX() for a string with the macro tr() attribute slot once to do the initial translation and then connect the setXXX() slot to an instance of LocaleHandler that emits a signal every time the language (or locale) changes. It's complicated by the fact that the LocaleHandler knows that the language has changed, but he doesn't know which key text to provide openings, it is attached to the then must fix the LocaleHandler signal to an intermediate location that knows what translation of key to use for this attribute, and then emits a different signal with the key as a parameter that must be connected to the slot machine control setXXX() . This means that, for every single control attribute you want live, translate you'll need a separate intermediate location set somewhere, a signal linked to this site and two calls QObject::connect(). For EACH attribute that we want to live translation. Of course, this becomes very ugly, very fast.

I prefer to use C++ with QML little or not to expose my app pages so I was determined to find a solution that was easier to use than retranslating in QML (or almost) and after some trial and error I came up with a solution that I am very satisfied. The core of this technique is a C++ class called LiveTranslator. The syntax to use is a bit more complicated to use QML re-translation, but as re-translation you only need to add a line of code for each attribute that you want to translate live. Here is the header for LiveTranslator:
```
#ifndef LIVETRANSLATOR_HPP_
#define LIVETRANSLATOR_HPP_

#include 

using namespace bb::cascades;

class LiveTranslator: public QObject {
    Q_OBJECT

    QString _key;
    QString _context;

    static LocaleHandler* _localeHandler;

public:
    LiveTranslator( const QString& context, const QString& key, QObject* target, const char* slot );
    static void setLocaleHandler( LocaleHandler* localeHandler );

private slots:
    void localeOrLanguageChangedHandler();

signals:
    void translate( const QString& string );
};

#endif /* LIVETRANSLATOR_HPP_ */
```
.. .and the body...
```
#include "LiveTranslator.hpp"

// ---Initialize the locale handler pointer on app startup so we can tell if it has been set properly later
LocaleHandler* LiveTranslator::_localeHandler = 0;

// ---Note that the target control is also used as the parent so the live translator dies when the control does
LiveTranslator::LiveTranslator( const QString& context, const QString& key, QObject* target, const char* slot ) :
        QObject( target ) {

    bool success;
    Q_UNUSED( success );

    // ---Save the context and key string
    this->_key = key;
    this->_context = context;

    // ---Die (during debug) if the locale handler hasn't been set properly before use
    Q_ASSERT( LiveTranslator::_localeHandler );

    // ---Watch for locale or language changes
    success = QObject::connect( LiveTranslator::_localeHandler, SIGNAL( localeOrLanguageChanged() ), SLOT( localeOrLanguageChangedHandler() ) );
    Q_ASSERT( success );

    // ---Trigger specified slot when locale or language changes
    success = QObject::connect( this, SIGNAL( translate( const QString& ) ), target, slot );
    Q_ASSERT( success );
}

void LiveTranslator::localeOrLanguageChangedHandler() {
    // ---Use the specified slot on the target to update the appropriate string attribute with the translated key
    emit translate( QCoreApplication::translate( this->_context.toLocal8Bit().constData(), this->_key.toLocal8Bit().constData() ) );
}

// ---This function MUST be called once with a valid LocaleHandler before any LiveTranslator classes are instantiated
void LiveTranslator::setLocaleHandler( LocaleHandler* localeHandler ) {
    LiveTranslator::_localeHandler = localeHandler;
}
```
LiveTranslator encapsulates all the ugly stuff, including remembering the key to the translation, the intermediate signal/slot, and all signal/slot connections necessary for direct translation. Use is as simple as creating an instance of LiveTranslator, passing the constructor the translation for the attribute key (and the context, but more on that later), the Visual control of the target and the location on the control that accepts the update of translation. Note that tr() only works with static keys chains...
```
// ---This is valid
QString str1 = tr("string one");

// ---This is not!
Qstring str1 = "string one";
QString str2 = tr(str1);
```
.. .so instead tr(), LiveTranslator must use QCoreApplication translate() internally.

An example of use of LiveTranslator :
```
MyClass::MyClass() {
    Label* label = Label::create().text( tr("Label one") );
    new LiveTranslator( "MyClass", "Label one", label, SLOT(setText(const QString&)));

    Option* option = Option::create().text( tr("Option one") ).description( tr("Option one description") );
    new LiveTranslator( "MyClass", "Option one", option, SLOT(setText(const QString&)));
    new LiveTranslator( "MyClass", "Option one description", option, SLOT(setDescription(const QString&)));

    ActionItem* actionItem = Option::create().title( tr("Action one") );
    new LiveTranslator( "MyClass", "Action one", actionItem, SLOT(setTitle(const QString&)));
}
```
Note that there is no need to save a reference to the new instance LiveTranslator since the constructor sets the 'target' as a parent control. When the control is destroyed by your app the LiveTranslator will go with him. The first parameter to the constructor LiveTranslator is the 'context' where the translation key. When you use the macro tr() (or function qsTr() QML) the code parser mentions of where he found the key and stores it in the translation file. This way you can use the same key for translation on different pages, and if the context is different, you could have them translated differently. The parser doesn't know anything about the LiveTranslator class but it must indicate the context explicitly. For C++, the context is always the name of the class containing the code that you are translating. In addition, in case it is not obvious, the "key" parameter must be the same value used with tr() on the input line.

There is one thing that you must do before using LiveTranslator in your C++ code and that is to give it a LocaleHandler to work with. Rather than force you to spend a LocaleHandler for each instance of LiveTranslator, you tell LiveTranslator that one to use only once with a static function call. If you created your application from one of the Momentics models then you already have a Manager, you can use:
```
ApplicationUI::ApplicationUI() : QObject() {
    // prepare the localization
    m_pTranslator = new QTranslator( this );
    m_pLocaleHandler = new LocaleHandler( this );

    // Use this locale handler for all the live translations too
    LiveTranslator::setLocaleHandler( m_pLocaleHandler );

    ...
    ...
    ...
}
```
I enclose the source for LiveTranslator so all you need to do to get the direct translation working in your BB10 native C++ code is extract the zip in your src directory, add a call to LiveTranslator::setLocaleHandler() in your main application class constructor, and then call new LiveTranslator (...) with the appropriate settings for each attribute of the control you want to be living translated. I hope that is useful to the native BlackBerry 10 development community wonderful (and long-suffering).

IMPORTANT!

The instructions posted above have been extended and improved to work with some additional user interface controls such as SystemDialog and SystemUiButton. It was published with a link to a sample application on GitHub as an guest article on the Blog of Dev of BlackBerry. Additional functionality has been added to the original code shown above, then the blog article and GitHub example now consider the definitive description of this technique.

See you soon.

* CRITICAL ERROR * Momentics - Editor could not be initialized

java.lang.OutOfMemoryError: Java heap space
    at java.util.Arrays.copyOf(Unknown Source)
    at java.lang.AbstractStringBuilder.expandCapacity(Unknown Source)
    at java.lang.AbstractStringBuilder.append(Unknown Source)
    at java.lang.StringBuilder.append(Unknown Source)
    at com.rim.tad.tools.qml.parser.ast.ASTUtils.indent(ASTUtils.java:233)
    at com.rim.tad.tools.qml.parser.ast.ASTUtils.access$0(ASTUtils.java:231)
    at com.rim.tad.tools.qml.parser.ast.ASTUtils$1.visit(ASTUtils.java:134)
    at com.rim.tad.tools.qml.parser.ast.ASTVisitor$Adapter.visit(ASTVisitor.java:223)
    at com.rim.tad.tools.qml.parser.ast.ASTVisitor$Adapter.visit(ASTVisitor.java:313)
    at com.rim.tad.tools.qml.parser.ast.ASTQMLNamedValue.accept(ASTQMLNamedValue.java:111)
    at com.rim.tad.tools.qml.parser.ast.ASTList.accept(ASTList.java:279)
    at com.rim.tad.tools.qml.parser.ast.ASTQMLObject.accept(ASTQMLObject.java:102)
    at com.rim.tad.tools.qml.parser.ast.ASTQMLNamedValue.accept(ASTQMLNamedValue.java:122)
    at com.rim.tad.tools.qml.parser.ast.ASTList.accept(ASTList.java:279)
    at com.rim.tad.tools.qml.parser.ast.ASTQMLObject.accept(ASTQMLObject.java:102)
    at com.rim.tad.tools.qml.parser.ast.ASTQMLNamedValue.accept(ASTQMLNamedValue.java:122)
    at com.rim.tad.tools.qml.parser.ast.ASTList.accept(ASTList.java:279)
    at com.rim.tad.tools.qml.parser.ast.ASTQMLObject.accept(ASTQMLObject.java:102)
    at com.rim.tad.tools.qml.parser.ast.ASTQMLNamedValue.accept(ASTQMLNamedValue.java:122)
    at com.rim.tad.tools.qml.parser.ast.ASTList.accept(ASTList.java:279)
    at com.rim.tad.tools.qml.parser.ast.ASTQMLObject.accept(ASTQMLObject.java:102)
    at com.rim.tad.tools.qml.parser.ast.ASTQMLNamedValue.accept(ASTQMLNamedValue.java:122)
    at com.rim.tad.tools.qml.parser.ast.ASTList.accept(ASTList.java:279)
    at com.rim.tad.tools.qml.parser.ast.ASTQMLObject.accept(ASTQMLObject.java:102)
    at com.rim.tad.tools.qml.parser.ast.ASTQMLNamedValue.accept(ASTQMLNamedValue.java:122)
    at com.rim.tad.tools.qml.parser.ast.ASTList.accept(ASTList.java:279)
    at com.rim.tad.tools.qml.parser.ast.ASTQMLObject.accept(ASTQMLObject.java:102)
    at com.rim.tad.tools.qml.parser.ast.ASTQMLNamedValue.accept(ASTQMLNamedValue.java:122)
    at com.rim.tad.tools.qml.parser.ast.ASTList.accept(ASTList.java:279)
    at com.rim.tad.tools.qml.parser.ast.ASTQMLObject.accept(ASTQMLObject.java:102)
    at com.rim.tad.tools.qml.parser.ast.ASTQMLNamedValue.accept(ASTQMLNamedValue.java:122)
    at com.rim.tad.tools.qml.parser.ast.ASTList.accept(ASTList.java:279)

At startup. Originally close the editor. How to solve this problem?

Criticism! Impossible to develop or access the qml files.

Also, try opening a new empty workspace. If you have disabled Momentics to invite the user to choose a workspace on startup, open the following file in a text editor:

bbndk-2.1\configuration\.settings\org. Eclipse.UI.IDE.prefs

And change:

SHOW_WORKSPACE_SELECTION_DIALOG = false

TO:

SHOW_WORKSPACE_SELECTION_DIALOG = true

And then try to start over Momentics and choose a new workspace.

Using C++ in QML classes in app without head: refers to 'bb::device:VibrationController:staticMetaObject' the undefined

Hi, I've been weeks of work on the BB and had a lot of problems. Some of them have been resolved, some were not without the support of the forum.

Now I have a great difficulty that I can't find answer by Googling.

I am grateful to some body can help.

Here's a simple case that make the big problem for me:

1. create an app without head with Momentics. 2 project will be generated HeadlessApp and HeadlessAppService.

Without modification, this code works well.

2. I'm link below to use VibrationController in HeadlessAppService: https://developer.blackberry.com/native/documentation/dev/integrating_cpp_qml/index.html#usingcclass...

below the code has been added:

-Add codes below to main.cpp HeadlessAppService

#include 
using namespace bb::device;

then add qmlRegisterType as below

Q_DECL_EXPORT int main(int argc, char **argv)
{

   Application app(argc, argv);

   qmlRegisterType("bb.vibrationController", 1, 0, "VibrationController");
   ApplicationUI appui;
   return Application::exec();
}

3. to confirm the new code, I just right click on the project and select build project.

Bang! I got several error I don't understand. (red lines are errors)

08:44:30 **** Incremental Build of configuration Device-Debug for project headlessTest ****
make -j4 Device-Debug
make -C .//translations -f Makefile update
make[1]: Entering directory 'D:/BB-dev/momentics-workspace/headlessTest/translations'
C:/bbndk/host_10_3_1_12/win32/x86/usr/bin/lupdate headlessTest.pro
Updating 'headlessTest.ts'...
    Found 2 source text(s) (0 new and 2 already existing)
make[1]: Leaving directory 'D:/BB-dev/momentics-workspace/headlessTest/translations'
make -C .//translations -f Makefile release
make[1]: Entering directory 'D:/BB-dev/momentics-workspace/headlessTest/translations'
C:/bbndk/host_10_3_1_12/win32/x86/usr/bin/lrelease headlessTest.pro
Updating 'D:/BB-dev/momentics-workspace/headlessTest/translations/headlessTest.qm'...
    Generated 0 translation(s) (0 finished and 0 unfinished)
    Ignored 2 untranslated source text(s)
make[1]: Leaving directory 'D:/BB-dev/momentics-workspace/headlessTest/translations'
make -C ./arm -f Makefile debug
make[1]: Entering directory 'D:/BB-dev/momentics-workspace/headlessTest/arm'
make -f Makefile.Debug
make[2]: Entering directory 'D:/BB-dev/momentics-workspace/headlessTest/arm'
qcc -Vgcc_ntoarmv7le -lang-c++ -Wl,-rpath-link,C:/bbndk/target_10_3_1_995/qnx6/armle-v7/lib -Wl,-rpath-link,C:/bbndk/target_10_3_1_995/qnx6/armle-v7/usr/lib -Wl,-rpath-link,C:/bbndk/target_10_3_1_995/qnx6/armle-v7/usr/lib/qt4/lib -Wl,-rpath-link,C:/bbndk/target_10_3_1_995/qnx6/armle-v7/usr/lib/qt4/lib -o o.le-v7-g/headlessTest o.le-v7-g/.obj/applicationui.o o.le-v7-g/.obj/main.o o.le-v7-g/.obj/moc_applicationui.o    -LC:/bbndk/target_10_3_1_995/qnx6/armle-v7/usr/lib/bb1 -LC:/bbndk/target_10_3_1_995/qnx6/armle-v7/lib -LC:/bbndk/target_10_3_1_995/qnx6/armle-v7/usr/lib -LC:/bbndk/target_10_3_1_995/qnx6/armle-v7/usr/lib/qt4/lib -LC:/bbndk/target_10_3_1_995/qnx6//usr/lib/qt4/lib -lbb -lbbsystem -lbbcascades -lQtDeclarative -lQtScript -lQtSvg -lQtSql -lsqlite3 -lz -lQtXmlPatterns -lQtGui -lQtNetwork -lsocket -lQtCore -lm -lbps
o.le-v7-g/.obj/main.o: In function `int qmlRegisterType(char const*, int, int, char const*)':
c:/bbndk/target_10_3_1_995/qnx6/usr/include/qt4/QtDeclarative/qdeclarative.h:191: undefined reference to `bb::device::VibrationController::staticMetaObject'
o.le-v7-g/.obj/main.o: In function `QDeclarativeElement':
c:/bbndk/target_10_3_1_995/qnx6/usr/include/qt4/QtDeclarative/qdeclarativeprivate.h:87: undefined reference to `bb::device::VibrationController::VibrationController(QObject*)'
o.le-v7-g/.obj/main.o:(.data.rel.ro._ZTVN19QDeclarativePrivate19QDeclarativeElementIN2bb6device19VibrationControllerEEE[_ZTVN19QDeclarativePrivate19QDeclarativeElementIN2bb6device19VibrationControllerEEE]+0x8): undefined reference to `bb::device::VibrationController::metaObject() const'
o.le-v7-g/.obj/main.o:(.data.rel.ro._ZTVN19QDeclarativePrivate19QDeclarativeElementIN2bb6device19VibrationControllerEEE[_ZTVN19QDeclarativePrivate19QDeclarativeElementIN2bb6device19VibrationControllerEEE]+0xc): undefined reference to `bb::device::VibrationController::qt_metacast(char const*)'
o.le-v7-g/.obj/main.o:(.data.rel.ro._ZTVN19QDeclarativePrivate19QDeclarativeElementIN2bb6device19VibrationControllerEEE[_ZTVN19QDeclarativePrivate19QDeclarativeElementIN2bb6device19VibrationControllerEEE]+0x10): undefined reference to `bb::device::VibrationController::qt_metacall(QMetaObject::Call, int, void**)'
o.le-v7-g/.obj/main.o:(.data.rel.ro._ZTIN19QDeclarativePrivate19QDeclarativeElementIN2bb6device19VibrationControllerEEE[_ZTIN19QDeclarativePrivate19QDeclarativeElementIN2bb6device19VibrationControllerEEE]+0x8): undefined reference to `typeinfo for bb::device::VibrationController'
o.le-v7-g/.obj/main.o: In function `~QDeclarativeElement':
c:/bbndk/target_10_3_1_995/qnx6/usr/include/qt4/QtDeclarative/qdeclarativeprivate.h:91: undefined reference to `bb::device::VibrationController::~VibrationController()'
c:/bbndk/target_10_3_1_995/qnx6/usr/include/qt4/QtDeclarative/qdeclarativeprivate.h:91: undefined reference to `bb::device::VibrationController::~VibrationController()'cc: C:/bbndk/host_10_3_1_12/win32/x86/usr/bin/ntoarm-ld caught signal 1
Makefile.Debug:103: recipe for target 'o.le-v7-g/headlessTest' failed
make[2]: *** [o.le-v7-g/headlessTest] Error 1make[2]: Leaving directory 'D:/BB-dev/momentics-workspace/headlessTest/arm'
make[1]: *** [debug] Error 2
Makefile:50: recipe for target 'debug' failed
make: *** [Device-Debug] Error 2make[1]: Leaving directory 'D:/BB-dev/momentics-workspace/headlessTest/arm'
mk/cs-base.mk:31: recipe for target 'Device-Debug' failed
08:44:31 Build Finished (took 1s.47ms)

I give up!

Why adding simple code can be a problem? Please help me!

Thank you very much!

You must add this code into main.cpp to your HeadlessApp, not HeadlessAppService. Your spare part cannot run any UI stuff, trying to save an object any for QML is part of the things in the user interface.

But anyway, reading your newspaper from the console, you seem to put in the right place anyway. Did you add this to your headlessTest.pro file:
LIBS +=-lbbdevice

Porting Qt for Qnx Momentics application

Hey, I wanted to know if its possible to transfer my Qt to the Qnx Momentics IDE application. I search everywhere to search to find the documentation or instuctions on how but cannot find information porting of Qt Creator

Basically, that's what I

I carried the Qt for Qt Creator application and have successfully got running on the Alpha of Dev

Now I want to:

1 import / move more Qt App to the IDE from Qnx

2. remove the Qt INTERFACE and rebuild the App for UI in the cascades while keeping the back end qt

So can I keep the rear end of Qt and rebuild this Interface in waterfalls?

If for anoyone can point me to the documentation on how I can move the porject in Qnx Momentics.

NOTE: Im fully aware im not able to mix code UI/Interface Qt with waterfalls. I have to choose one or the other. in this case, I want to replace the user of Qt interface with waterfalls

Thanks in adavnce, happy coding and porting

Yes, QDE is QNX Momentics IDE. I think it is easier to move their inverse:

Create a new project in Momentics, and then move the source one of the old project files in new (with the exception of the classes related to the GUI). And then recreate the GUI.

On QT Creator / waterfalls:

To set up QT Creator, follow the steps on the wiki:

http://Qt-project.org/wiki/setting-up-Qt-Creator-for-BlackBerry-and-QNX

I think you have already done this.

Then create a Qt Quick project (wiki describes this step).

After that remove all Qt Quick related features of the project and add libraries of stunts in the .pro file. This is how my project file looks like this:
```
TEMPLATE = app

# Please do not modify the following line.
#include(qmlapplicationviewer/qmlapplicationviewer.pri)

# Additional import path used to resolve QML modules in Creator's code model
QML_IMPORT_PATH =

QT += declarative script xmlpatterns xml sql network svg

INCLUDEPATH += src

# Workaround for autocompletion bug
INCLUDEPATH += include include/cpp include/qt4/QtCore include/qt4/QtSql include/qt4/QtNetwork

LIBS += -lbbcascades -lbbcascadesmultimedia -lbbdevice -lbbplatform -lbbpim -lbbdata -lbbcascadespickers -lbbsystem -lbbmultimedia

# The .cpp file which was generated for your project. Feel free to hack it.
SOURCES += main.cpp \
   ...other cpp files...

OTHER_FILES += bar-descriptor.xml \
    qml/main.qml

HEADERS += \
   ...header files...
```
Then update file bar - descriptor.xml. You can use the Momentics generated file as a template. Here's my bar - descriptor.xml (replace application_name and paths):
```
http://www.qnx.com/schemas/application/1.0">
    com.mydomain
    Application Name
    1.0.0
    Application Description
    
        none
        false
        true
        portrait
    
    
    
    
    run_native
    MyApplication
    qml
    assets
    
        assets/images/icons/applicationIcon114.png
    
    
       assets/images/splash/portrait768x1280.jpg
       assets/images/splash/portrait720x1280.jpg
    
```
After this attempt to create and deploy a simple project of Cascades. If everything is ok, start moving your old project files (file-by-file).

Important:

AutoComplete does not work initially. All stunts and Qt classes will be highlighted in red.

Wiki describes some workaround solutions. The one I use is create a symbolic link in your project file to point to the ndk includes the folder:

lrwxr-xr-x @ staff 1 user 55 15 Dec 19:23 include->/Applications/bbndk/target_10_0_9_1673/qnx6/usr/include

Then, add the following line to the .pro file:
```
INCLUDEPATH += include include/cpp include/qt4/QtCore include/qt4/QtSql include/qt4/QtNetwork
```
Autocompletion should work after that. I use Qt Creator on MacOS, this may not apply to the version of Windows.

What do you see when you run that this basic example ListView QML?

I read through the examples of ListView found here:

http://developer.BlackBerry.com/native/reference/Cascades/bb__cascades__ListView.html

I'm at the part that speaks of "'How to create a list in QML and access a variable inside the ListView". " When I run the example, I see a ListView display the data I entered model.xml. But must I also see "Example text" added on each entry in ListView? I don't see "Example text" displayed anywhere.

The property type must match the xml in the template tag, for example:

Using this model in xml format:

With this qml code works perfectly:

import bb.cascades 1.3

Page {
    ListView {
        property string myText: "is a City"
        dataModel: XmlDataModel {
            source: "model.xml"
        }
        listItemComponents: [
            ListItemComponent {
                type: "item"
                CustomListItem {
                    id: itemRoot
                    dividerVisible: true
                    highlightAppearance: HighlightAppearance.Full
                    Container {
                        Label {
                            text: ListItemData.title + " " + itemRoot.ListItem.view.myText
                        }
                    }
                }
            }
        ]
    }
}

Order of the Momentics IDE links

Hi all

I have faced the problem of link order while strengthening the application with 2 static libraries.

I have 1 request and 2 static library projects in the workspace. A library is dependent on the other.

To get the app connected successfully, it is important to link the libraries in the order you want.

How can I specify the order of the libraries that would be used to link the application? I tried to change the order in the file .pro without a bit of luck.

I am using Momentics version 2.1 Build id: 201406041640 on Mac OS X 10.9.4.

Thank you

Anton

There is a work around for this problem. After you add libraries, assign the property "automatically generate the config.pri" to "Never automatically generate" or "Prompt" on the properties (context menu) > QML > QML properties page, and then change the libraries order in the config.pri by replacing manually.

Qt Creator 3.0 as an alternative to Momentics

Hello

is anyone using Qt Creator to create stunts app? It is possible since version 3.0. I tried shortly after the exit and realized that it works. There however not e. g. seized semiautomatic for Cascades classes in code QML. He is also unable to highlight typos. I think that it shouldn't be so hard to make this work.

Apart from that, I think that Qt Creator is much more convenient than Momentics IDE. For example, all shortcuts work as expected (F3 to find a string, Ctrl + Tab to switch between editors...)

No one answered my major problem with QCompass, so I have to answer me:

In this case, it was useful to compare the Makefile generated by Qt Creator to the Makefile generated by Momentics. I was copying the lines of the latter to the former, and rebuild the project. In this way, I was able to overcome the differences down to a single one that was causing the problem:

-DQ_OS_BLACKBERRY on the line starting by SETS

I added the definition of file *.pro and now everything works fine.

play a sound custom 'discharge of the battery' and events 'battery full '.

IM developing an application for the status of battery... I used class BatteryInfo why... I added a switch box qml to get the status of battery on specific event... now I want to add sound to the full battery and battery...

Help, please

Thank you

looking at your code return you something, then play you the sound.
code after a return is not executed.

Yes, you can access the label using findChild, but it would be a new question for a new thread.

Momentics IDE appears to hang in debug mode

Hey. I just started using Momentics IDE 2.1.1 with the 10.3.1.2267 simulator, and after getting an error message (I'll come back to that) panels of FDI seem stuck in debug with the debugging in the top pane on the left. I pressed Stop, the big red button, and it doesn't seem to work. I want to go back to available to panels with the code in the main central panel. (It says done in the message in the debug pane)

Grateful help ny

See you soon

Justin D.

P.s. The backs do BB apps after a few years away, good to be back.

Do you mean that Momentics does not meet the entry or it does not change in the Debug Perspective for the C/C++ editor QML prospects after debugging is complete?

The prospect does not change automatically once debugging is complete. To switch to a different perspective use the buttons at the top right of the toolbar or go to the window menu and choose Open Perspective and then C/C++ or QML edition.

get the problem when starting native/cascades beta sdk - "QML preview is not available.

Hello friends,

When I start native/cascades sdk beta (latest version). It shows an error message "QML previw is not available. I am also attaching the screenshot of it. And my PC has no external graphics card.

Please tell me why I get this message?

Thank you best regards &,.

Dinesh

Hello dinesh,

Looks like you don't have a graphics device that supports the preview mode. You must have a fairly modern graphics chipset with sufficient support to use the live preview Momentics openGL. Details are provided in the section 'Manufacturer of Cascades' to https://developer.blackberry.com/cascades/download/releasenotes/. Unfortunately, unless you upgrade your graphics card, you should probably use the Simulator or device to display your user interface.

Tim

QML code completion?

I just installed the QNX Momentics IDE and created a new project of "Hello World" of cascades. When I change the 'hellocascades.qml' I get no code completion.

Who is wrong?

It works for me .

Hit results Ctrl + Space in a window to appear with a list of attributes can be defined for a given element.

If this does not work then please reply back with some details of what is happening:

(1) your operating system

(2) the code and the location slider where you try to use the code completion/assits

Why my editor QML doesn't show list predictive method?

I once saw a video that shows the QML poster Publisher predictive when method list type '. '.

But that does not show my editor QML. I have to manually check the API reference. Do you know how to enable this feature?

My version of the IDE's® of QNX Momentics® IDE for BlackBerry® 10 native SDK Version: 10.0.9

In addition, it can show the list of predictive methods in the RPC editor without problem.

Thanks for helping me.

CTRL + space

Momentics qml full fon

Similar Questions

Maybe you are looking for