Hmmm - this message has been sitting in my outbound mail queue for 2 or
3 days - sorry for the late reply.
Thanks Neil (and everyone else who replied). This has been a great help.
Monte's right - this would be a great example for a community effort (if
his efforts on the engine forum don't le
On 04/05/2013, at 8:39 AM, Monte Goulding wrote:
> Yeah... I presume there was no choice but I'm not really sure why the LC
> activity isn't dealing with orientation in the onConfigurationChanged
> method... I'll ask on the engine forum.
I'm chasing this up here:
http://forums.runrev.com
On 04/05/2013, at 8:26 AM, Alex Tweedly wrote:
> Do you need to ? Wouldn't it be enough to do
> device=Amazon
> orientation_map=0,90
>
> Or are there other Amazon devices which don't have that same orientation ?
I don't know... I guess we would need to physically have each device in our
> BUT
> it never exits the repeat loop early
> and
> it never resets t_this_device
>
I think the idea is RunRev have a default file (which I can't find in the
runtime folder) and prefix it to the user's file so that the user's file
overrides RunRevs
--
Monte Goulding
M E R Goulding - softw
On 03/05/2013 13:40, Monte Goulding wrote:
On 03/05/2013, at 10:25 PM, Guglielmo Braguglia wrote:
- KFOT = Kindle Fire
- KFTT = Kindle Fire HD 7"
- WFJWI = Kindle Fire HD 8.9" Wi-Fi
- WFJWA = Kindle Fire HD 8.9" WAN
I haven't done much LC android work.. only Java. The file format seems poorly
OK, I know it's been a while since I looked seriously at C or C++ code,
but .
it looks to me as though this loops through all the lines in the array
when it finds a matching device it sets t_this_device to (presumably) true
if it gets an orientation_map line and t_this_device is true, then i
> I'll try and poke around the engine to find this. If it doesn't work the
> way I said I might submit a pull request to make it do that because it
> makes sense...
Here's the relevant code from the engine. As you can see it will match the
first device line it can to the device then the first subs
I'll try and poke around the engine to find this. If it doesn't work the way I
said I might submit a pull request to make it do that because it makes sense...
There could be hundreds of devices with that orientation map. Your point about
you only having the one device is where I was going with t
Hi Monte,
never tried, but ... reading the "Android Release Notes", Pag. 29, I
think that you have to do something like that :
device=Amazon|KFOT|||
orientation_map=0,90
device=Amazon|KFTT|||
orientation_map=0,90
device=Amazon|WFJWI|||
orientation_map=0,90
device=Amazon|WFJWA|||
orientation_map
On 03/05/2013, at 10:25 PM, Guglielmo Braguglia wrote:
> - KFOT = Kindle Fire
> - KFTT = Kindle Fire HD 7"
> - WFJWI = Kindle Fire HD 8.9" Wi-Fi
> - WFJWA = Kindle Fire HD 8.9" WAN
I haven't done much LC android work.. only Java. The file format seems poorly
documented. Can I have a file like
Ah .. I forget ...
... this is for the *Kindle Fire HD 7" NO WiFi* ... so, you have to
change the *KFTT* (in the .txt file) following this table :
- KFOT = Kindle Fire
- KFTT = Kindle Fire HD 7"
- WFJWI = Kindle Fire HD 8.9" Wi-Fi
- WFJWA = Kindle Fire HD 8.9" WAN
Guglielmo
On 5/3/13 14:02 P
Hi Alex,
enclosed you will find the file that you MUST add to your stack
(Standalone Application Settings -> Copy Files - > Add File) and ... the
Kindle Fire is ok :-)
Guglielmo
On 5/3/13 00:59 AM, Alex Tweedly wrote:
I'm just starting to play with Mobile builds - so this could be the
first
On 03/05/2013, at 7:36 PM, n...@runrev.com wrote:
> More information on this can be
> found on page 28 of the Android Release notes under "Device Specific
> Orientations"
That page says there's a default file in the runtime folder but I don't see
one. Which repo would this be in? Perhaps this w
Hi Alex,
I believe the issue you are experiencing is due to the way the kindle fire
handles it orientations.
To rectify this, you will need to create a config file that informs your
application of the correct orientations. More information on this can be
found on page 28 of the Android Release no
On 5/2/13 8:16 PM, Ralph DiMola wrote:
Alex,
Remember also that "portrait upside down" and "landscape left" are not
supported on Android 2.2 or earlier. This might account for the upside down
thing. Flip it the other way in the emulator and it might just work.
That was my first thought too, bu
Alex,
Remember also that "portrait upside down" and "landscape left" are not
supported on Android 2.2 or earlier. This might account for the upside down
thing. Flip it the other way in the emulator and it might just work.
Ralph DiMola
IT Director
Evergreen Information Services
rdim...@evergreenin
can't help with the orientation at the moment, but the problem with the
virtual devices is that you've most likely selected 2.2 as your build
target, and are using 2.2 virtual devices. go to 2.3 or 2.3.3. The way
some of the sensors are handled in the 2.2 emulator don't work right (real
devices wo
17 matches
Mail list logo
