[TIMOB-1638] iOS: enhancement to removeProperty - make it synchronous
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Trivial |
| Status | Closed |
| Resolution | Invalid |
| Resolution Date | 2012-07-25T16:14:51.000+0000 |
| Affected Version/s | Release 1.5.0 |
| Fix Version/s | n/a |
| Components | iOS |
| Labels | n/a |
| Reporter | ctredway |
| Assignee | Neeraj Gupta |
| Created | 2011-04-15T02:58:03.000+0000 |
| Updated | 2012-07-26T22:23:15.000+0000 |
Description
a premium customer reported the following:
I read that property setting has been made asynchronous (https://twitter.com/titanium_github/status/21614464002)">https://twitter.com/titanium_github/status/21614464002), can this pleeeeze also be applied to 'removeProperty', as I have a series of complex properties I need to 'clear out' and it seems to be generating many threads when it does.
Comments
- ctredway 2011-04-15
Ok, the customer clarified what they meant.
I meant to say the removeProperty is currently asynchronous and setting property values was recently made synchronous. So can the removeProperty also be made synchronous.
- Stephen Tramer 2012-07-25
Description does not contain enough information
Code does not indicate that property setting via the likely candidate
Ti.App.Propertiesis synchronous.