oh...i read misread the statement. it means that if datachanged is
emitted, then there is a surety that the data has been set. that
really had me very confused at one point of time.. :)
Regards,.
saurabh
On 10/6/11, Aaron J. Seigo wrote:
> On Thursday, October 6, 2011 20:46:14 Saurabh Sood wrote
On Thursday, October 6, 2011 20:46:14 Saurabh Sood wrote:
> quite get the point, where you said that when a source appears, it may
> not have all data in place.
DataEngines are asynchronous. there is no guarantee as to when the data will
arrive from them, just that it will at some point in the fu
Aaron,
I was facing the same problem some time back. i used
onSourceAdded:connectSource(source) and got it working. I did not
quite get the point, where you said that when a source appears, it may
not have all data in place.
Regards,.
Saurabh
On 10/6/11, Aaron J. Seigo wrote:
> On Thursday, Octo
On Thursday, October 6, 2011 10:05:47 Marco Martin wrote:
> On Thursday 06 October 2011, Viranch Mehta wrote:
> > Hi all,
> >
> > I am facing a very annoying problem in QML plasmoids with the dataengines.
> > The following does not seem to work ever for almost all dataengines:
> >
> > PlasmaCore.
On Thursday 06 October 2011, Viranch Mehta wrote:
> Hi all,
>
> I am facing a very annoying problem in QML plasmoids with the dataengines.
> The following does not seem to work ever for almost all dataengines:
>
> PlasmaCore.DataSource {
> id: dataSource
> engine: "someEngine"
> onSou
Hi all,
I am facing a very annoying problem in QML plasmoids with the dataengines.
The following does not seem to work ever for almost all dataengines:
PlasmaCore.DataSource {
id: dataSource
engine: "someEngine"
onSourceAdded: print (data[source]["some_valid_key"];
}
The print statem
