I would like to draw your attention to the CSendUi API in the S60 3rd
edition SDK.
It requires a huge amount of capabilities to be used (LocalServices,
NetworkServices, ReadDeviceData, WriteDeviceData, ReadUserData and
WriteUserData). The whole point however of using this API is to create a
one-shot message, like an email or a bluetooth send of a file or something
like that. It has methods for showning a Send command in a menu, and for
presenting a list of transports, which can be manipulated in all kinds of
usefull ways.
To add injury to insult, one-shot message sending was not supposed to be
burdened with all kinds of capabilities, because the user himself would
initiate such sending through a command, commonly a Send as command in a
menu.
So here I am, with an exe linking four dll's, all *needing* a Capability
None.
Sigh.
And on top of this, the CSendAppUi destructor crashes when you add an
attachmant, making the interface rather pointless.
--
Sander van der Wal
www.mBrainSoftware.com
Hi Sander
Attention drawn. I've fowarded internally for comment. If I get any I'll
post a response.
Regards
H
"Sander van der Wal" <[email protected]> wrote in message
news:[email protected]...
> I would like to draw your attention to the CSendUi API in the S60 3rd
> edition SDK.
>
> It requires a huge amount of capabilities to be used (LocalServices,
> NetworkServices, ReadDeviceData, WriteDeviceData, ReadUserData and
> WriteUserData). The whole point however of using this API is to create a
> one-shot message, like an email or a bluetooth send of a file or something
> like that. It has methods for showning a Send command in a menu, and for
> presenting a list of transports, which can be manipulated in all kinds of
> usefull ways.
>
> To add injury to insult, one-shot message sending was not supposed to be
> burdened with all kinds of capabilities, because the user himself would
> initiate such sending through a command, commonly a Send as command in a
> menu.
>
> So here I am, with an exe linking four dll's, all *needing* a Capability
> None.
>
> Sigh.
>
> And on top of this, the CSendAppUi destructor crashes when you add an
> attachmant, making the interface rather pointless.
>
> --
> Sander van der Wal
> www.mBrainSoftware.com
>
>
On second thought ... this is a Nokia S60 API, not a Symbian API. While I'm
pretty sure I agree with your analysis, raising it with Nokia would be the
best starting place.
Regards
H
"Hamish Willee" <[email protected]> wrote in message
news:[email protected]...
> Hi Sander
> Attention drawn. I've fowarded internally for comment. If I get any I'll
> post a response.
> Regards
> H
>
> "Sander van der Wal" <[email protected]> wrote in message
> news:[email protected]...[color=green]
> > I would like to draw your attention to the CSendUi API in the S60 3rd
> > edition SDK.
> >
> > It requires a huge amount of capabilities to be used (LocalServices,
> > NetworkServices, ReadDeviceData, WriteDeviceData, ReadUserData and
> > WriteUserData). The whole point however of using this API is to create a
> > one-shot message, like an email or a bluetooth send of a file or[/color]
something[color=green]
> > like that. It has methods for showning a Send command in a menu, and for
> > presenting a list of transports, which can be manipulated in all kinds[/color]
of[color=green]
> > usefull ways.
> >
> > To add injury to insult, one-shot message sending was not supposed to be
> > burdened with all kinds of capabilities, because the user himself would
> > initiate such sending through a command, commonly a Send as command in a
> > menu.
> >
> > So here I am, with an exe linking four dll's, all *needing* a Capability
> > None.
> >
> > Sigh.
> >
> > And on top of this, the CSendAppUi destructor crashes when you add an
> > attachmant, making the interface rather pointless.
> >
> > --
> > Sander van der Wal
> > www.mBrainSoftware.com
> >
> >
>
>[/color]
"Hamish Willee" <[email protected]> wrote in message
news:%[email protected]...
> On second thought ... this is a Nokia S60 API, not a Symbian API. While
> I'm
> pretty sure I agree with your analysis, raising it with Nokia would be the
I had done so, but I figured that others would be interested in such things,
for example it would help preventing these issues from occuring in the
future.
--
Sander van der Wal
www.mBrainSoftware.com
> best starting place.
> Regards
> H
>
> "Hamish Willee" <[email protected]> wrote in message
> news:[email protected]...[color=green]
>> Hi Sander
>> Attention drawn. I've fowarded internally for comment. If I get any I'll
>> post a response.
>> Regards
>> H
>>
>> "Sander van der Wal" <[email protected]> wrote in message
>> news:[email protected]...[color=darkred]
>> > I would like to draw your attention to the CSendUi API in the S60 3rd
>> > edition SDK.
>> >
>> > It requires a huge amount of capabilities to be used (LocalServices,
>> > NetworkServices, ReadDeviceData, WriteDeviceData, ReadUserData and
>> > WriteUserData). The whole point however of using this API is to create
>> > a
>> > one-shot message, like an email or a bluetooth send of a file or[/color]
> something[color=darkred]
>> > like that. It has methods for showning a Send command in a menu, and
>> > for
>> > presenting a list of transports, which can be manipulated in all kinds[/color]
> of[color=darkred]
>> > usefull ways.
>> >
>> > To add injury to insult, one-shot message sending was not supposed to
>> > be
>> > burdened with all kinds of capabilities, because the user himself would
>> > initiate such sending through a command, commonly a Send as command in
>> > a
>> > menu.
>> >
>> > So here I am, with an exe linking four dll's, all *needing* a
>> > Capability
>> > None.
>> >
>> > Sigh.
>> >
>> > And on top of this, the CSendAppUi destructor crashes when you add an
>> > attachmant, making the interface rather pointless.
>> >
>> > --
>> > Sander van der Wal
>> > www.mBrainSoftware.com
>> >
>> >
>>
>>[/color]
>
>[/color]