Re: VS: Re: maemopad exits suddenly when clicking on Save icon
Thank you. But as I know, on the target device (N800), it works only with ARMEL architecture, is it right? If so, it's unnecessary to use X86 arch, it's for testing purpose. In the end, I'll need to transfer the app to N800 device. I just don't know what's wrong with this OS2008 version. I'm thinking about downgrading to OS2007. Too bad, right? OS2008 looks nice... On Feb 19, 2008 1:51 AM, Julius Luukko [EMAIL PROTECTED] wrote: Hi Jakov, You have to rebuild your application for X86 architecture. You are now trying to run an ARMEL binary with X86. So make clean; make -- Julius - Alkuperäinen viesti - Lähettäjä: Jakov [EMAIL PROTECTED] Vastaanottaja: [EMAIL PROTECTED], maemo-developers@maemo.org Lähetetty: Ma 18 Helmi 2008 09:40:30 Aihe: Re: maemopad exits suddenly when clicking on Save icon Thank you, I also have Chinook X_86. Is it supposed to work? In fact, I tried to switch to X_86 target. But when I ran maemopad, it said: /scratchbox/tools/bin/misc_runner: SBOX_CPUTRANSPARENCY_METHOD not set Could you do me a favor by telling me how to set it up? Thanks a lot! On Feb 18, 2008 4:23 PM, [EMAIL PROTECTED] wrote: Jakov wrote: I'm using Maemo 4.0 Chinook. After I load maemopad, click on Save icon, this application suddenly exits. The msg in the console is: [sbox-CHINOOK_ARMEL: ~/maemopad-2.1] run-standalone.sh src/maemopad qemu: Unsupported syscall: 264 This is the problem, you need a version of qemu w/ support for more of the arm cpu. Please keep in mind that the ARMEL environment is designed for cross compiling, not for hosting/testing. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers Liitetiedosto: ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Segmentation fault in callback functions - maemo 4.0
Jakov wrote: Oops, installed the old deb file. Now I repack my app to new .deb file. But I can't install with this file, the problem reported: Unable to install testapp Application packages missing: hildon-fm1 (=1.14) hildon-libs0 (=0.14.11-1) libdbus-1-2 (=0.61) - Does it mean N800 miss above packages? ITOS2008 / Maemo 4.0 does not have those packages, yes. See http://repository.maemo.org/stable/chinook/3.2_vs_4.0_content_comparison.html Maemo documentation will probably help with details, but I assume you'll want to use libdbus-1-3, hildon-1 and hildon-fm-2. HTH, Jussi ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Using the scrollbar on the N810
Hi, ext Richard Booth wrote: Is there a hidden setting somewhere to improve the scrollbar sensitivity in the web browser on the N810? I find it tricky to use the web browser in full screen mode. If I try to grab the bar with the stylus and scroll down I can end up leaving the scroll bar behind, with a series of clicks and sometimes the scrolling goes the opposite way. It seems that scrolling is either too sensitive or not sensitive enough. I've recalibrated and tested the screen with maemoplus, and it picks up a tap accurately on the right and across the screen (except near the top left web icon area), but scrolling is frustrating. I find it particularly awkward at the times when you want to fast scroll down a page. I really wish the N810 had a scroll wheel I'm not sure whether this helps, but you can scroll the page with long-press of the down key in keyboard. Short press moves just to next link. or a setting to improve the sensitivity or adjust the scrollbar width. How do others find it? - Eero ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
How to disable screen saver in SDL?
Hi, i have a little sdl app which i use to test my tiltstick. Since the tiltstick is none of the typical input mechanisms it doesn't reset the timout of the screen saver. How can i trigger the screen saver from a pure sdl application? Till ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Using the scrollbar on the N810
Frantisek Dufka wrote: Neil MacLeod wrote: Richard Booth wrote: How do others find it? Rich Exactly the same as you - when I grab the scrollbar thumbtrack, instead of the events being processed by the scrollbar widget the events appear to be processed by the main page of the application At least on my device this is due to erratic touchscreen. Try to install maemopadplus, turn off toolbar so there is no scrollbar and try to 'drag scrollbar'. At least on my device I always have beginning of the line moved to the left so it looks like T or 1. This means the first tap is interpreted inside main page. Please report it in bugzilla if you have time. Frantisek Bug 2961[1] now opened for what it's worth... I've inadvertently assigned it to the incorrect component (input method framework) when it should be Window Manager (I think) - perhaps someone would be kind enough to reassign? After further investigation this problem is not due to the thumbtrack - simply dragging within the scrollbar region OUTSIDE the thumbtrack will result in the drag events being passed to the main application. I suspect I've often been missing the thumbtrack in the past and thus hitting this bug - ideally the window manager would allow for a few extra pixels above and below the thumbtrack widget when determining if it's been clicked upon! 1. https://bugs.maemo.org/show_bug.cgi?id=2961 ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: How to disable screen saver in SDL?
ext Till Harbaum / Lists wrote: Hi, i have a little sdl app which i use to test my tiltstick. Since the tiltstick is none of the typical input mechanisms it doesn't reset the timout of the screen saver. How can i trigger the screen saver from a pure sdl application? You can use libosso, see function disable_display_blank() in : http://www.google.com/codesearch?hl=enq=+enk_init.c+show:LphOR0hsj4o:k-6gweQTR0E:6xyP0otZaZksa=Ncd=2ct=rccs_p=https://garage.maemo.org/frs/download.php/180/hh_source.tar.bz2cs_f=hedgehopper/libenkine/enk_init.c#first Till ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers // Tapani Pälli -- Software Engineer Open Source Software Operations ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
RE: Using the scrollbar on the N810
Richard Booth wrote: I find it particularly awkward at the times when you want to fast scroll down a page. I really wish the N810 had a scroll wheel Eero wrote: I'm not sure whether this helps, but you can scroll the page with long-press of the down key in keyboard. Short press moves just to next link. And if you don't like the link navigation, you can disable it ... http://timeless.justdave.net/maemo/microb-pageupdown-0.1.deb ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Installing directly onto internal memory card
Hi, thanks, that's what i do now. Till Am Sonntag 17 Februar 2008 schrieb Charles Werbick: You can use the pre-install script to do what you need. But you need to make sure your post-removal script cleans it up. hope this helps, charles werbick On 2/17/08, Till Harbaum / Lists [EMAIL PROTECTED] wrote: Hi, I'd like to install some data of a game directly onto the internal memory card. Unfortunately the installer doesn't seem to be able to create the files there as it's a fat file system. The installer fails with the message that it cannot preserve the file permissions (which is true as fat cannot do this). Can one circumvent this? There isn't much inside a deb file that makes me think this is possible. How can data be installed directly onto a memory card? Regards, Till ___ 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: Using the scrollbar on the N810
Neil wrote: Bug 2961[1] now opened for what it's worth... I've inadvertently assigned it to the incorrect component (input method framework) when it should be Window Manager (I think) - perhaps someone would be kind enough to reassign? After further investigation this problem is not due to the thumbtrack - simply dragging within the scrollbar region OUTSIDE the thumbtrack will result in the drag events being passed to the main application. I suspect I've often been missing the thumbtrack in the past and thus hitting this bug - ideally the window manager would allow for a few extra pixels above and below the thumbtrack widget when determining if it's been clicked upon! 1. https://bugs.maemo.org/show_bug.cgi?id=2961 Unfortunately, this isn't really how things work. Either a widget asks to capture input, in which case it can get events outside its boundaries, or it doesn't. If a widget does ask to capture events outside its boundaries, it then needs to have some idea about what to do with them. And that's hard (and each group will implement it differently, but poorly) ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Segmentation fault in callback functions - maemo 4.0
Oh, I see. Thanks, Jussi. Now I can install the application. However, it turns to the above problem. When I click a button, the application exits with error: Segmentation fault. Then let's turn to Eero Tamminen's question: I guess in that case there's a bug in your application. Was it also a segfault like with Qemu? Does it output any Glib asserts to syslog (on device) or to console (on x86 Sbox)? If you Valgrind it on x86 sbox, does it output any errors from your application? I don't think there's any new bug, because the app worked well on Maemo 3.2before. With this new maemo, I just make again and run. Ah, I also modify some include lines of code for suitable with new hildon. is it a problem related to qemu? Any hint for me? Thanks, On Feb 19, 2008 3:49 PM, Jussi Kukkonen [EMAIL PROTECTED] wrote: Jakov wrote: Oops, installed the old deb file. Now I repack my app to new .deb file. But I can't install with this file, the problem reported: Unable to install testapp Application packages missing: hildon-fm1 (=1.14) hildon-libs0 (=0.14.11-1) libdbus-1-2 (=0.61) - Does it mean N800 miss above packages? ITOS2008 / Maemo 4.0 does not have those packages, yes. See http://repository.maemo.org/stable/chinook/3.2_vs_4.0_content_comparison.html Maemo documentation will probably help with details, but I assume you'll want to use libdbus-1-3, hildon-1 and hildon-fm-2. HTH, Jussi ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Using the scrollbar on the N810
[EMAIL PROTECTED] wrote: Neil wrote: Bug 2961[1] now opened for what it's worth... I've inadvertently assigned it to the incorrect component (input method framework) when it should be Window Manager (I think) - perhaps someone would be kind enough to reassign? After further investigation this problem is not due to the thumbtrack - simply dragging within the scrollbar region OUTSIDE the thumbtrack will result in the drag events being passed to the main application. I suspect I've often been missing the thumbtrack in the past and thus hitting this bug - ideally the window manager would allow for a few extra pixels above and below the thumbtrack widget when determining if it's been clicked upon! 1. https://bugs.maemo.org/show_bug.cgi?id=2961 Unfortunately, this isn't really how things work. Either a widget asks to capture input, in which case it can get events outside its boundaries, or it doesn't. If a widget does ask to capture events outside its boundaries, it then needs to have some idea about what to do with them. And that's hard (and each group will implement it differently, but poorly) Hi Josh - I'm guessing your reply concerns my comment about the thumbtrack capturing events slightly above/below and not the bug being discussed (2961)? If so I can understand what you're saying - it would just be nice if the scrollbar were able to allow for slightly mis-directed tocuhscreen hits! Ultimately I guess scrollbars will disappear to be replaced by more finger friendly drag/kinetic scrolling so improving thumbtrack hit detection isn't such a big deal, but fixing the broken click drag event processing certainly is something which needs fixing. I have tested bug 2961 on a 770 running OS 2007HE and Opera, and it is not present. And on a N810, bug 2961 doesn't appear to be present with other applications such as the RSS Feed Reader (which also supports page drag scrolling) so perhaps bug 2961 is in fact an EAL/MicroB issue? ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
PyGTK/Hildon: CLOSING CHILD WINDOW PROPERLY?
I am trying to convert my command-line Python program into a PyGTK/Hildonized version for my Nokia N800. I am *very new* at doing this, so the best that I can do is look for examples that other people have written, and this is what I have been using for my 'child' window, but it does not work -- since when I close the window my entire application ends: def button_clicked(widget, data): window2 = hildon.Window() window2.connect(destroy, gtk.main_quit) label = gtk.Label(blah) label.set_text(You clicked on button +data+!!!) label.show() window2.add(label) window2.show() return Can anyone tell me the 'trick' of being able to close a 'child' window without the entire application shutting down? Thanks! Dare ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: undefined symbol: _Py_TrueStruct
It was something wrong with my N800, because now, magically,it works on N800 and also in scratchbox: I've uploaded a tgz with the deb packages compiled for i386 and armel http://eclectico.net/python-hildondesktop-plugin-0.0.2.tar.gz On Feb 18, 2008 6:19 PM, Lauro Moura [EMAIL PROTECTED] wrote: On 2/14/08, Sergio Galán [EMAIL PROTECTED] wrote: Thanks, The code works, but only inside scratchbox, not in the N800. In Scratchbox I see all the error messages so I can try to solve the problems, but, ¿Does someone know how to see error messages from graphical applications which are running on the N800? It's a home desktop plugin, so I can't run it from commandline... Probably it's a typo in my patch: It should be libpython2.5.so.1.0, not only .so (which is inside -dev package). -- Lauro Moura INdT - Instituto Nokia de Tecnologia ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: PyGTK/Hildon: CLOSING CHILD WINDOW PROPERLY?
Hi there. On Tue, Feb 19, 2008 at 09:49:12AM -0600, Darren Enns wrote: window2.connect(destroy, gtk.main_quit) It looks to me like gtk.main_quit() will be called each time the window is destroyed, thus killing the all application. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: PyGTK/Hildon: CLOSING CHILD WINDOW PROPERLY?
Daniel Martin Yerga wrote: Try changing the line: window2.connect(destroy, gtk.main_quit) with: window2.connect(destroy, window2.destroy) You have more information about gtk.main_quit function in: http://pygtk.org/docs/pygtk/gtk-functions.html#function-gtk--main-quit Yippee doodle! :) Thanks for that! I had been on the page that you referenced, convinced that I should not really be doing a 'gtk.main_quit', but I didn't see any syntax/examples like 'window.destroy' as you mentioned. I would really like more tutorials written at my level of understanding :) Dare ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: PyGTK/Hildon: CLOSING CHILD WINDOW PROPERLY?
On Tue, 2008-02-19 at 09:49 -0600, Darren Enns wrote: I am trying to convert my command-line Python program into a PyGTK/Hildonized version for my Nokia N800. I am *very new* at doing this, so the best that I can do is look for examples that other people have written, and this is what I have been using for my 'child' window, but it does not work -- since when I close the window my entire application ends: [snip] window2.connect(destroy, gtk.main_quit) [snip] Get rid of that line :) --Chris ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: PyGTK/Hildon: CLOSING CHILD WINDOW PROPERLY?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi. On Tue, 19 Feb 2008 09:49:12 -0600 Darren Enns [EMAIL PROTECTED] wrote: I am trying to convert my command-line Python program into a PyGTK/Hildonized version for my Nokia N800. I am *very new* at doing this, so the best that I can do is look for examples that other people have written, and this is what I have been using for my 'child' window, but it does not work -- since when I close the window my entire application ends: def button_clicked(widget, data): window2 = hildon.Window() window2.connect(destroy, gtk.main_quit) label = gtk.Label(blah) label.set_text(You clicked on button +data+!!!) label.show() window2.add(label) window2.show() return Can anyone tell me the 'trick' of being able to close a 'child' window without the entire application shutting down? Try changing the line: window2.connect(destroy, gtk.main_quit) with: window2.connect(destroy, window2.destroy) You have more information about gtk.main_quit function in: http://pygtk.org/docs/pygtk/gtk-functions.html#function-gtk--main-quit Regards. - -- Daniel Martin Yerga http://yerga.net -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHuvz1cnvB1T3xmfMRAvSrAJkBfWVdm3DaVEM+izrwyx3xCPSoPQCeOhzY DE6E6WeIIeBIbnkQocKkNZ4= =ktrq -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
RE: Using the scrollbar on the N810
Neil wrote: Hi Josh - I'm guessing your reply concerns my comment about the thumbtrack capturing events slightly above/below and not the bug being discussed (2961)? If so I can understand what you're saying - it would just be nice if the scrollbar were able to allow for slightly mis-directed tocuhscreen hits! Ultimately I guess scrollbars will disappear to be replaced by more finger friendly drag/kinetic scrolling I'm not sure how practical this is for full web browsers. I know everyone says ooh look shiny when they look at iPhone/iPod touch, but the fact is that if you need to be able to allow full integration w/ Google Maps and the rest of Google's applications (note: Apple cheats by shipping their own Google Maps UI), then trying to trap user interactions is a disaster (which is quite visible from the bad compromises we've made for the tablet browser). For any other application that doesn't have to host full applications (i.e. flash embedded into an application has the same problem as a web browser), then finger friendly whatever may be better, but those aren't my problem spaces, and I don't own ui design, so I'm staying away from them. so improving thumbtrack hit detection isn't such a big deal, but fixing the broken click drag event processing certainly is something which needs fixing. Some of our problems relate to trying to counteract some bad kernel/x behaviors (they're fixed in newer internal builds, which means we can remove some of our bad hacks), and some of them stem from trying to implement bad design decissions from the platform (dragging a web application with a finger, see earlier complaints). If you're looking for another case where things don't work correctly, try typing into google reader's main screen using the n810's keyboard. I have tested bug 2961 on a 770 running OS 2007HE and Opera, and it is not present. And on a N810, bug 2961 doesn't appear to be present with other applications such as the RSS Feed Reader (which also supports page drag scrolling) so perhaps bug 2961 is in fact an EAL/MicroB issue? I was pretty sure that the bad dragging/scrolling hacks were in microb-eal, but I can't find them... ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
