change softkey shortcuts on an "installing-SIS-file application"

[wizard_hu_]

Let us practise reading:

...
S60 3rd Edition
To get the emulator display the reason and error code for panics, start the emulator, then open its Tools -> Preferences menu, and finally make sure the "Extended panic code file" option is checked on the C++ Debug tab. (This has the effect of creating a zero-sized file named ErrRd (no file name extension) under the PC's directory %EPOCROOT%\epoc32\wins[cw|b]\c\resource\.)

On the device, you should create a zero-sized file ErrRd (no file name extension) under the directory c:\resource\. You can use a file explorer application (for instance, FExplorer) to create the file, or if none is available, use a signed sis file. In case you don't want to use ErrRd, then you could also use Y-Tasks Crash monitor.

You can obtain a prebuilt sis file from here (file signature updated, valid until 2018)
...

The red thing is a link on that page.

[Paul.Todd]

Lets get the panic code before doing anything more.

My guess is ShortcutMaker need to be an active object that is kicked off when the active scheduler is started and stopped when the shortcut is completed.

[mike_p]

Ok, after practising some reading, I installed Y-Tasks and got this:

Main KERN-EXEC: 3

[mike_p]

Hi Paul.Todd, I think that your prognosis is wrong, due to the fact that the application crashes during this:

iShortcut = CScShortcutEngineWrapper::NewL(iSession,*this);

And regarding this,

You need to delay and retry until your application is found

, i've tried to delay using Getch() (before the instantiation of ShortcutMaker) , it still crashes.

[Paul.Todd]

My advice still stands:
-Put your class into an active object.
-Use 2 phase construction so that you know the object's VMT is correctly setup before it is potentially used
-Schedule the active object
-Start the active scheduler
-Let the active object actually do the change once the list has completed initializing.
-Its possible though unlikely as its such a small program (according to the code shown), you might have run out of stack space
(see http://wiki.forum.nokia.com/index.ph...60_3rd_Edition)

You have so many things that are different both from the solution provided in the example, from our own implementation which I know works and from standard Symbian c++ that I have no idea or time to work out which is wrong without a lot of unpaid investigation.