Usually it's just easier to buidl the application on a real linux box or a virtual machine.
Type: Posts; User: laa-laa; Keyword(s):
Usually it's just easier to buidl the application on a real linux box or a virtual machine.
The async service provider --- CTelephony in this case --- sets iStatus to KRequestPending. However, it does not add the active object to the active scheduler's list of outstanding requests. That's...
You'll need to call CActive.:SetActive() yourself when you issue a request involving CActive::iStatus.
I suggest trial and error. I can't access the build environment I set up last time anymore to check on details.
Just run the tests and run gcov (or any other compatible report generator). If it...
ViewSrv 11 panic implies there's something blocking the active scheduler loop from running.
Some things to check:
- long-running active objects
- high-priority, busy active objects
- mixing...
You create a new project that produces a test executable and has
QT += testlib
in it's project file. The test code itself should be in a QObject and include a call to QTest::qExec() - usually...
Hint: "a" is a member variable of type sms in class gui and also a local variable of type sms* in gui::gui() constructor.
It's a feature of Symbian and not really a bug. The reason is already there in post #5: \private directory itself is not accessible (without AllFilles capability) while \private\youruid is. Checking...
It's because the \private directory itself is not accessible (without AllFilles capability) while \private\youruid is.
Note that the code snippets you linked to are not complete examples. You'll need to put the code in a function.
Do you have
#include <eikenv.h>
somewhere in the compilation unit?
_L() is in practice a convenienve wrapper for TPtrC. Using it in the usual way creates a temporary TPtrC object on stack consuming 8 bytes of space (descriptor length and flags in 32 bits, pointer to...
To me it seems to be an issue with misbehaving compiler trigraph sequences. Trigraphs are three-character sequences starting with ?? and are turned into an alternative character symbol by the...
Hi, I noticed your question on stackoverflow first and also answered it there.
Sounds like a stack overflow.
Note that stack space for local variables is allocated at function scope, not block scope. Some ways to fix the issue:
- split the cases into separate helper...
Not directly. You'll need to wrap the Symbian C++ code in Qt C++ code and expose the Qt C++ API into QML, for example using a Q_INVOKABLE function.
This error usually occurs when you try to compile the MOC-generated file as a regular source/header file. For example, having something like
SOURCES += *.cpp
HEADERS += *.h
will easily lead...
You can use the QSettings constructor variant that takes in a file name to supply it with a path that is guaranteed to be in your private data cage (\private\<uid> directory). For example:
...
That's how the AppUi Exit() is implemented: it leaves with KLeaveExit. In order for the exit mechanism to work, you should propagate the KLeaveExit leave to the UI framework active scheduler loop...
A const variable is still a variable and not a compile-time constant. Stack-based allocation needs to know the space requirements at compile time. To allocate dynamically, use heap-based allocation...
@danhicksbyron: ... which shouldn't be used with Qt since it's from the old ESTLIB standard library. Instead one should use the PIPS/Open C one in epoc32\include\stdapis.
epoc32/include/stdapis should be in INCLUDEPATH by default anyway so despite the extra space there, the original error is most probably somewhere else. Which header files are missing?
It's a filesystem difference. Your simulator is running on a filesystem where directories always have "." and ".." entries. The filesystem on N8 does not have such entries.
For that kind of purpose I suggest you use a version control tool with automated build environment that always builds your releasable packages the same way, preferably starting with a clean SDK. It's...
I'm not using Nokia Qt SDK - I've found it to be too simplified for my needs. Instead I'm using Qt on regular S60 SDKs. These S60 SDK flags work there as far as I know.
For your case, since the...