[TIMOB-802] Ti.include relative paths are always from the app root
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Medium |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2011-04-17T01:54:17.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | Release 1.4.0 |
| Components | Android |
| Labels | android, defect, include |
| Reporter | Marshall Culpepper |
| Assignee | Marshall Culpepper |
| Created | 2011-04-15T02:36:44.000+0000 |
| Updated | 2011-04-17T01:54:17.000+0000 |
Description
.. instead of from the directory of the file that is calling Ti.include
I can confirm this is cross-platform prob. Problem in iPhone too (I noticed it was only tagged for android here, so I thought maybe it wasn't clear that it's also cross-platform.)
Also, dupe of #503.
(from [47d9e1b75cc4dd4c20374fbc90cd9529cf7d7b61]) use a stack to manage the relative location of Ti.include paths (since we don't always associate a context with them) [#802 state:resolved] http://github.com/appcelerator/titanium_mobile/commit/47d9e1b75cc4dd4c20374fbc90cd9529cf7d7b61"> http://github.com/appcelerator/titanium_mobile/commit/47d9e1b75cc4d...
Marshall / Don
I think this was a duplicate of #503, wasn't it?
Please note my comment at the end of #503, which describes a similar bug with relative imageView urls. Are you aware of this? Do we need to raise a fresh ticket for it?
Thanks
Hal