[ALOY-750] Can't use a pipe separator (bitwise operator) in TSS for some API's that require it
GitHub Issue | n/a |
---|---|
Type | Improvement |
Priority | Medium |
Status | Closed |
Resolution | Fixed |
Resolution Date | 2013-08-08T13:53:11.000+0000 |
Affected Version/s | Alloy 1.1.2 |
Fix Version/s | Alloy 1.3.0 |
Components | Styling |
Labels | qe-testadded |
Reporter | Rick Blalock |
Assignee | Tony Lukasavage |
Created | 2013-07-17T13:46:16.000+0000 |
Updated | 2013-10-14T19:06:27.000+0000 |
Description
this causes a compiler error when doing this in a TSS file:
windowSoftInputMode: Ti.UI.Android.SOFT_INPUT_STATE_HIDDEN | Ti.UI.Android.SOFT_INPUT_ADJUST_PAN
Per docs, this should be possible: http://docs.appcelerator.com/titanium/3.0/#!/api/Titanium.UI.Window-property-windowSoftInputMode
A workaround for this would be doing the bitwise operation in the alloy.js, adding this as a property to Alloy.Globals, then using the property in the TSS. It's unwieldy, but will work until a fix is in place.
PR: https://github.com/appcelerator/alloy/pull/215 test app: https://github.com/appcelerator/alloy/tree/master/test/apps/testing/ALOY-750 For functional test to pass:
Run the test app for android
Ensure that the compile process does not generate errors (it did before this was resolved)
Check the generated code in "Resources/alloy/controllers/index.js" and make sure that the main window has the following in its construction properties:
In addition, the full automated test suite should be run to ensure that there are no regressions in the TSS handling due to the grammar changes.
Verified fixed. TiSDK 3.2.0.v20131013140318 Alloy 1.3.0 Android simulator 2.3.3 and Google Nexus One 4.1.2 Closing