Send buglog mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.openmoko.org/mailman/listinfo/buglog
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of buglog digest..."
Today's Topics:
1. Re: Openmoko Bug #1315: xglamo: Performance decreases after a
while (Openmoko Public Trac)
2. Re: Openmoko Bug #1549: [exposure] want to launch exposure
again while it is in the e-illume bar, need 5~10 sec
(Openmoko Public Trac)
3. Re: Openmoko Bug #1549: [exposure] want to launch exposure
again while it is in the e-illume bar, need 5~10 sec
(Openmoko Public Trac)
4. Re: Openmoko Bug #1238: SIM card contacts not displayed
(Openmoko Public Trac)
5. Re: Openmoko Bug #1533: The keypad shows brackets number in
dialer screen and creat new message (Openmoko Public Trac)
6. Re: Openmoko Bug #1549: [exposure] want to launch exposure
again while it is in the e-illume bar, need 5~10 sec
(Openmoko Public Trac)
7. Openmoko Bug #1654: Qwerty keyboard launcher in ASU
(Openmoko Public Trac)
8. Openmoko Bug #1655: Remove button no longer removes apps
(Openmoko Public Trac)
--- Begin Message ---
#1315: xglamo: Performance decreases after a while
-------------------------------------+--------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: openmoko-devel
Type: defect | Status: new
Priority: highest | Milestone: ASU
Component: Xfbdev (kdrive), Xglamo | Version: unspecified
Severity: critical | Resolution:
Keywords: | Blocking:
Blockedby: |
-------------------------------------+--------------------------------------
Changes (by tick):
* cc: [EMAIL PROTECTED] (added)
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1315#comment:9>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1549: [exposure] want to launch exposure again while it is in the e-illume bar,
need 5~10 sec
------------------------+---------------------------------------------------
Reporter: wendy_hung | Owner: marek
Type: defect | Status: assigned
Priority: normal | Milestone: ASU
Component: E - Illume | Version:
Severity: normal | Resolution:
Keywords: must have | Blocking:
Blockedby: |
------------------------+---------------------------------------------------
Comment(by marek):
1. It may be the case that I move a little but why is the onclick
animation shown ? That should only happen if we have a click or is this a
onmousedown which can become a click or a drag ?
2. Yes, I catch the signal. As I explained earlier the window comes to the
front but it takes some time. I used the normal python handler to get the
signal. May be that conflicts with your main loop somehow. How do I get
ecores sigusr ?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1549#comment:11>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1549: [exposure] want to launch exposure again while it is in the e-illume bar,
need 5~10 sec
------------------------+---------------------------------------------------
Reporter: wendy_hung | Owner: marek
Type: defect | Status: assigned
Priority: normal | Milestone: ASU
Component: E - Illume | Version:
Severity: normal | Resolution:
Keywords: must have | Blocking:
Blockedby: |
------------------------+---------------------------------------------------
Comment(by raster):
1. its an onmousedown that starts the green animation, but it is a mouse
UP that ends the action. as between the mouse down and up you may or may
not drag - the whole action may become either a click (a down then up with
minimal movement) OR it becomes a drag (at which point it should not
activate the selected item). same thing as in the etk scrolledview before
- e has this and it has tuning parameters to determine what is a drag and
what is just a regular click+release. thus why i suggest you play with the
settings :)
2. aaah you set your own signal handler. and i guess you call activate()
from the signal handler? bad! signal handlers are just as bad as threads.
they can interrupt anything - preemptively and when they return do nothing
special. so the same explanation for threads not working above counts for
signal handlers. in fact signal handles should do almost nothing - or as
little as possible. don't use a signal handler, OR use ecore's signal
handler wrappers (that convert signals to events). they were created for
just this reason - that signal handlers are unreliable to use for any
serious work, but if you just use them as signallers and then from there
add events into an event queue - and process the event queue in the main
loop as normal... it works fine.
so... you need some way of doing this without threads or signal handlers
(or sysv ipc... i could start to think of other messaging/signalling
systems you also dont want to use). you want a socket or a fd/pipe or
something else.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1549#comment:12>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1238: SIM card contacts not displayed
-----------------------------------------+----------------------------------
Reporter: [EMAIL PROTECTED] | Owner: [EMAIL PROTECTED]
Type: defect | Status: reopened
Priority: highest | Milestone:
Component: Applications & Dependencies | Version: unspecified
Severity: normal | Resolution:
Keywords: OpenMoko | Blocking:
Blockedby: |
-----------------------------------------+----------------------------------
Comment(by montgoss):
These are two separate issues. This bug is where there are NO contacts
displayed.
1639 is what happens on the newest daily builds where only some contacts
off the SIM are displayed.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1238#comment:15>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1533: The keypad shows brackets number in dialer screen and creat new message
------------------------+---------------------------------------------------
Reporter: wendy_hung | Owner: zecke
Type: defect | Status: new
Priority: highest | Milestone: ASU
Component: Qtopia | Version:
Severity: blocker | Resolution:
Keywords: keypad | Blocking:
Blockedby: |
------------------------+---------------------------------------------------
Comment(by kenrestivo):
I had this same problem, but it was intermittent. Haven't had it in a
while, and I religiously do an opkg update; opkg upgrade every day.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1533#comment:7>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1549: [exposure] want to launch exposure again while it is in the e-illume bar,
need 5~10 sec
------------------------+---------------------------------------------------
Reporter: wendy_hung | Owner: marek
Type: defect | Status: assigned
Priority: normal | Milestone: ASU
Component: E - Illume | Version:
Severity: normal | Resolution:
Keywords: must have | Blocking:
Blockedby: |
------------------------+---------------------------------------------------
Comment(by marek):
1. That means I can mousedown on one item and get the animation. Then I
move my finger and nothing happens ? That seems pretty bad ...
I wrote a little patch for etk_list in our ninja theme to avoid this kind
of problems. It creates an after_animation hook that you can grab. So,
onmouseup launch the animation and then you wait for the signal from edje.
Tick installed some ugly timeouts to get the same effect - that is why I
provided that patch some weeks ago. I hope he applied it.
I attach the patch here.
2. Why is E so weak in handling asynchronous events ? Is that a design
decision, a X11 limitation or what ? I'm used to use all the godies my
linux world offers to me. ;-)
How do I use the ecore's wrapper to get the signal ? Any documentation or
example available ?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1549#comment:13>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1654: Qwerty keyboard launcher in ASU
------------------------+---------------------------------------------------
Reporter: kenrestivo | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version: GTA02v5
Severity: normal | Keywords:
Blocking: | Blockedby:
------------------------+---------------------------------------------------
I was delighted a day or to ago when I opkg upgraded and it added a neat
new feature: a "qwerty" button appeared in the pull-down menu, and I could
click on it to get a keybaord anywhere I needed one! So VTE and minimo
were finally useful.
I opkg update; opkg upgraded today, and that feature is gone!
Please bring it back! I loved it. It finally made the FR useful for me.
Now it is not again.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1654>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1655: Remove button no longer removes apps
------------------------+---------------------------------------------------
Reporter: kenrestivo | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version:
Severity: normal | Keywords:
Blocking: | Blockedby:
------------------------+---------------------------------------------------
The "REMOVE" button in the pull down menu at the top of ASU screens used
to work to kill apps. It no longer does. I can select it, it highlights, I
can press it, but nothing happens. The apps never die. Once I start an
app, even by accident, I'm stuck with it until I reboot the phone. Apps
have become like a Halloween monster, they cannot be killed.
This is using today's ASU update.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1655>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
