Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-1961] Orientation change event only fires once

GitHub Issuen/a
TypeBug
PriorityMedium
StatusClosed
ResolutionFixed
Resolution Date2011-04-17T01:57:40.000+0000
Affected Version/sn/a
Fix Version/sRelease 1.5.0
ComponentsiOS
Labels1.4.2, change, d1, defect, ios, iphone, orientation
Reporterctredway
AssigneeBlain Hamon
Created2011-04-15T03:06:34.000+0000
Updated2011-04-17T01:57:40.000+0000

Description

On the iPhone, sdk 4.x and 1.4.2 (and earlier) the orientation change only fires once.

see this ticket for code and history.
http://developer.appcelerator.com/helpdesk/view/45371">http://developer.appcelerator.com/helpdesk/view/45371

Comments

  1. Stephen Tramer 2011-04-15

    Strongly recommending that the engineering team discuss this behavior. There is a major problem with resolving this bug, namely that we need to make sure that behavior is consistent across both iPhone and Android platforms when dealing with event listeners at the module level.

    Secondly, we will need to retain any possible contexts which involve event listeners, and listeners will affect ONLY those contexts, i.e. they may not work as expected for variables with the same name across contexts. Resolving this issue could take major changes to how Kroll callbacks work within Titanium and will require that some critical resources are never released (contexts for closed pages).

    Going to mark needs-more-info and begin discussion with engineering.

  2. Stephen Tramer 2011-04-15

    Two separate things here:

    1. What appears to be at least part of the bug described in the HD ticket has been confirmed as fixed. Closing a context which originally contained a gesture listener, then adding a new gesture listener in a different context, works as expected. This is bug #2048. I have independently confirmed that the sample code provided by the customer is functional off of the latest master/HEAD.
    2. The issue described above, handling when module event listeners can be added and how long they should be expected to persist, has been agreed upon by engineering to have the correct behavior at present.

    Marking this ticket resolved as a result.

JSON Source