Re: QT map widget
kate.alh...@nokia.com wrote: Situation is when lot of map tiles are loaded. loaded as in downloaded? About the number of tiles loaded into memory, mappero uses a tile cache, which is actually quite big (140 tiles, and tiles are textures sized 256x256 pixels) so it may consume quite a bit of memory. But in my case, according to top the RSS is about 21MB, which doesn't seem so scary. I dont't know what internaly happens. Some memory leak ? For application performance and cpu usage also time needed for tile pre-processing need to be counted. I doubt there are any substantial memory leaks, I've been using mappero for several hours without breaks, and didn't notice any worsening. Does it some scaling for tiles after loading them ? No, it does only if the tile of the needed size is missing. But that's something you can notice quite easily, because it's quite evident when the pixels are being doubled. Finally time used for scaling tiles is one key issues. Do we scale them or download every size. How much cpu power is used for scaling or do we leave it all for GPU ? Every size is downloaded. Scaling happens rarely, and it is done on the CPU; but after scaling the texture is stored into the GPU and reused, so the performance hit is minimal. For mappero case i don't know how much cpu is used for actual scaling and how much by exhausting virtual memory ? I'm not sure about virtual memory, but about CPU mappero will never use more than 30-35% -- it simply isn't allowed by the OS (startup times could be much faster if it were...). Ciao, Alberto -- http://blog.mardy.it -- geek in un lingua international! ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Qt Mobility Contacts - bugs?
Hi, On 14/06/10 06:39, ext Felipe Crochik wrote: Has anybody tried modifying the database on the n900 using the qt mobility? Am I missing something or is it really a bug? how do you start your application? Are you doing it remotely with the Nokia Qt SDK? There was an issue, as it starts the application with the developer, and not with the user account. This caused issues with the contacts part of Qt Mobility. For more information have a look at the forum discussion [1] about that topic. 1. http://talk.maemo.org/showthread.php?t=53820page=4 Daniel ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: How to get kinetic scrolling working using Qt creator
Hi Sudheer! It's a very sad decision to give up on such simple thing. Thanks, Daniil. On Mon, Jun 14, 2010 at 7:49 AM, Sudheer K. scifi@hotmail.com wrote: Hi Daniil, From the testing I have done with latest Qt designer, scrolling is still not working. Somehow, I am not able to get the scrolling working with your .ui file too. But I feel at this point we have spent too much time for a non-critical issue such as this. Right now I am using tabs to organize the form fields and I will continue to use it. Scrolling would have been nice but is not absolutely necessary. Thank you for staying with this thread and continuously responding to my questions. ~Sudheer Date: Thu, 10 Jun 2010 10:20:56 +0300 Subject: Re: How to get kinetic scrolling working using Qt creator From: daniil.iva...@gmail.com To: scifi@hotmail.com CC: maemo-developers@maemo.org Hi Sudheer! It should be something like .ui file in attachment. Thanks, Daniil. On Thu, Jun 10, 2010 at 10:14 AM, Daniil Ivanov daniil.iva...@gmail.com wrote: Hi Sudheer! The name of a tool is Qt Designer and it should allow to do what you want, however I'm wrong person to ask how to use Qt Designer. Thanks, Daniil. On Thu, Jun 10, 2010 at 7:47 AM, Sudheer K. scifi@hotmail.com wrote: Hi Daniil, Thanks for looking into the code. The main problem I have is that, Qt creator does not give enough flexibility to create the hierarchy that you suggested. This is the hierarchy created using Qt creator. http://i49.tinypic.com/2rxbm75.jpg - centralWidget is automatically created by Qt creator and is locked, so I cannot even delete it. - scrollAreaWidgetContents is also automatically created by Qt creator and is locked. I cannot modify this too. - I created two groupboxes (Basic and Advanced) which contain one form layout each. These are added to the scrollAreaWidgetContents because I can not directly add them to scrollArea. I am using Qt Creator 1.3.1. Is there a way to make the scrolling work using Creator or should I stop using Qt creator and code the form class myself? Date: Wed, 9 Jun 2010 18:33:55 +0300 Subject: Re: How to get kinetic scrolling working using Qt creator From: daniil.iva...@gmail.com To: scifi@hotmail.com CC: maemo-developers@maemo.org Hi Sudheer! There are many bugs there. For example you don't need centralWidget at all, place scrollArea instead of it. Then you create multiple layout, set them to widgets and never place them into scrollArea. On desktop you don't have scroll bars as well. Thanks, Daniil. The New Busy is not the too busy. Combine all your e-mail accounts with Hotmail. Get busy. Hotmail is redefining busy with tools for the New Busy. Get more from your inbox. See how. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Qt Mobility Contacts - bugs?
Hi Felipe, It works fine.. Daniel is right you have to run that application as user. Antonio On Mon, Jun 14, 2010 at 6:39 AM, Felipe Crochik fel...@crochik.com wrote: I believe I found one bug with the Qt Mobility Contacts but it seems that the bugreports.qt.nokia.com web site is out and because I can only verify it on the n900 I decide to report it here, at least to start with. The following code will add a new contact but this new contact will not b available on the standard contacts application. I verified that it gets saved somewhere because if you quit the application and start again you can find the contact using the id generated the first time. The standard contacts application still reports the same number of contacts before running this code and I can't find the contact on the list. code QContactManager manager; QContact contact; QContactName name; name.setFirstName(John); name.setLastName(Doe); contact.saveDetail(name); manager.saveContact(contact); qDebug() localid: contact.localId(); /code Has anybody tried modifying the database on the n900 using the qt mobility? Am I missing something or is it really a bug? ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
RE: Qt Mobility Contacts - bugs?
Daniel/Antonio: Thanks! In the heat of my tests I just did not think about it. Felipe -Original Message- From: daniel wilms [mailto:daniel.wi...@nokia.com] Sent: Monday, June 14, 2010 3:45 AM To: ext Felipe Crochik Cc: maemo-developers@maemo.org Subject: Re: Qt Mobility Contacts - bugs? Hi, On 14/06/10 06:39, ext Felipe Crochik wrote: Has anybody tried modifying the database on the n900 using the qt mobility? Am I missing something or is it really a bug? how do you start your application? Are you doing it remotely with the Nokia Qt SDK? There was an issue, as it starts the application with the developer, and not with the user account. This caused issues with the contacts part of Qt Mobility. For more information have a look at the forum discussion [1] about that topic. 1. http://talk.maemo.org/showthread.php?t=53820page=4 Daniel ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: QT map widget
Dnia 2010-06-13, nie o godzinie 14:39 +0300, Alberto Mardegan pisze: (off topic: if you can find some way to reproduce it reliably, please file a bug -- although if you really need to take out the battery, that cannot be a bug in the application itself) I had similar problem and even filled a bug: https://bugs.maemo.org/show_bug.cgi?id=9743 Could not reproduce it with PR1.2 so closed it. If you want to you can reopen it - I will gladly test some use cases. Regards. -- Tomasz Rybak bogom...@post.pl GPG/PGP key ID: 2AD5 9860 Fingerprint A481 824E 7DD3 9C0E C40A 488E C654 FB33 2AD5 9860 http://member.acm.org/~tomaszrybak signature.asc Description: This is a digitally signed message part ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
hildon.Program.set_common_toolbar not working
Hello everybody, I'm trying to develop with Hildon/PyGTK, and I'm quite confused by the /set_common_toolbar/ function of the hildon.Program class: it's supposed to set a gtk.Toolbar that will appear on every hildon.Window registered with the hildon.Program. Yet, the toolbar doesn't show up on my registered windows... I reminded to call show_all() on every window. Also, I can't just window.add it in each window, because I would then have to reparent the toolbar... Is there something special I forgot to make /set_common_toolbar/ work? Best, ~Stéphane ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
