I just like to sound like I know what I am talking about.
Bob S
> On Aug 31, 2017, at 16:14 , Mark Wieder via use-livecode
> wrote:
>
> I also want to give a shout out to the supportive community here. This is by
> far the best online community I've ever had the honor of being a part of. Th
KeyboardActivated is working. However, getting the effective working screenrect
is not producing a result different from the screenrect, meaning it does reveal
the available space after the keyboard pops up.
Sent from my iPhone
> On Sep 1, 2017, at 7:57 AM, Roger Eller via use-livecode
> wrot
Well, since the bug report indicates that keyboardActivated/keyboardDeactivated
messages were added to Android, if they are not working please report it.
If you want to just use a general rule for a 'safe zone', then prompting at
the top of the screen should work fine.
~Roger
On Fri, Sep 1, 2017
Hi Roger - yup, this problem affects other development environments too. Many
have complained about it online. I currently force the input into the top half
of the screen. Do you think I should force it even higher?
I could just make the input go to the very top when a user enters it.
Sent from
That's awesome! Thank you.
On Fri, Sep 1, 2017 at 7:24 AM, panagiotis merakos via use-livecode <
use-livecode@lists.runrev.com> wrote:
> @Roger according to BZ, this appears to be fixed:
>
> http://quality.livecode.com/show_bug.cgi?id=10410
>
> @Jonathan if this is not the case, could you file
The android version is 6.0.1.
Sent from my iPhone
> On Sep 1, 2017, at 6:46 AM, jonathandly...@gmail.com wrote:
>
> Hi Jacqueline,
>
> Sadly, that did not help. It received the KeyboardActivated message, and I
> had it check the effective working screenrect both at that point and again in
>
@Roger according to BZ, this appears to be fixed:
http://quality.livecode.com/show_bug.cgi?id=10410
@Jonathan if this is not the case, could you file a bug report so as we
keep track of this issue?
Best,
Panos
--
On Fri, Sep 1, 2017 at 12:20 PM, Roger Eller via use-livecode <
use-livecode@lists
This appears to be an old problem (2012). I don't know if there was ever a
solution. A best practice was to position any input fields in the top
third of the screen. I agree with the consensus that it should be handled
automatically, but it is not, obviously.
https://www.mail-archive.com/use-li
Hi Jacqueline,
Sadly, that did not help. It received the KeyboardActivated message, and I had
it check the effective working screenrect both at that point and again in a
handler set to trigger a second later. They all return results as if the
keyboard is not there.
This is on a galaxy tab E, w
What happens if you check the effective working screenrect in a
keyboardActivated handler?
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On August 31, 2017 8:04:45 PM Jonathan Lynch via use-livecode
wrote:
Actually, never mind, that cannot be it.
I tried the follow script:
on mouseUp
create field "test height"
select after field "test height"
send getEWSR to me in 1 second
end mouseUp
on getEWSR
answer the effective working screenrect
delete field "test height"
end getEWSR
it still return
A question for Mark Waddingham...
Mark, in my app, in the place in question, the keyboard is activated by a
browser widget. Is it possible that this means it is not sending a signal to LC
to update the value of the effective working screen rect?
Sent from my iPhone
> On Aug 31, 2017, at 8:27 P
Yes - it makes me want to share whatever I can.
Sent from my iPhone
> On Aug 31, 2017, at 7:14 PM, Mark Wieder via use-livecode
> wrote:
>
>> On 08/31/2017 07:33 AM, Jonathan Lynch via use-livecode wrote:
>> Just a random comment - having the CTO of LC directly answer our questions
>> is an
On 08/31/2017 07:33 AM, Jonathan Lynch via use-livecode wrote:
Just a random comment - having the CTO of LC directly answer our questions is
an incredible benefit to LC developers.
I also want to give a shout out to the supportive community here. This
is by far the best online community I've
On 08/31/2017 07:33 AM, Jonathan Lynch via use-livecode wrote:
Just a random comment - having the CTO of LC directly answer our questions is
an incredible benefit to LC developers.
...and not just answering questions, but expounding on the reasoning
behind existing features/bugs and brainstor
Hi Mark,
Unfortunately, the screen rect and the effective working screen rect return the
exact same results on this Android device - 0,0,800,1280.
Do you have any other suggestions for determining the keyboard height on
Android? I am willing to pursue my hack, but it is a pretty rough hack.
Se
Just a random comment - having the CTO of LC directly answer our questions is
an incredible benefit to LC developers.
Thanks Mark
Sent from my iPhone
> On Aug 31, 2017, at 10:22 AM, jonathandly...@gmail.com wrote:
>
> I have not tried that - wow, that could really help. I will check later toda
I have not tried that - wow, that could really help. I will check later today!
Sent from my iPhone
> On Aug 31, 2017, at 9:51 AM, Mark Waddingham via use-livecode
> wrote:
>
>> On 2017-08-31 15:34, jonathandly...@gmail.com wrote:
>> I can work with getting a snapshot just from the browser widg
On 2017-08-31 15:34, jonathandly...@gmail.com wrote:
I can work with getting a snapshot just from the browser widget, for
my particular case. As long as it also includes the keyboard in the
image.
Have you tried 'the [[effective] working] screenRect'?
I think 'the effect working screenRect' sh
Hi Mark,
I am trying to hack together a way to detect the height of the keyboard on
Android. My plan is to have an image 1-pixel wide, but full height of the
screen, with an rgb color of 0,0,1.
If the snapshot includes the keyboard, then the image data of the snapshot will
include a point whe
On 2017-08-31 14:25, Mark Waddingham via use-livecode wrote:
https://developer.apple.com/documentation/uikit/uiview/1622589-drawviewhierarchyinrect
Turns out this works quite well! It certainly manages to capture
a browser widget on iOS which is displaying the google homepage.
There is still a
Hi Jonathan,
On 2017-08-31 14:09, Jonathan Lynch via use-livecode wrote:
Thanks for checking Paul. It appears that, with a browser widget on
screen, I am only getting an image from the parts of the screen with
the browser widget.
With import snapshot, the non-browser parts of the image are
tran
Thanks for checking Paul. It appears that, with a browser widget on screen, I
am only getting an image from the parts of the screen with the browser widget.
With import snapshot, the non-browser parts of the image are transparent (and
black). With exporting a snapshot to a variable and putting t
I just ran a quick test and it works OK for me using LC8.1.6 on MacOS Sierra
10.12.6, build for iOS10 and tested on iPhone 5s running iOS10.3.3
HTH
Paul
> On Aug 30, 2017, at 7:00 PM, Jonathan Lynch via use-livecode
> wrote:
>
> I am getting all black in the image, but I checked and the rec
I am getting all black in the image, but I checked and the rect is the correct
rect.
Sent from my iPhone
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preference
25 matches
Mail list logo