Re: Setting the Cursor to an image

[hh via use-livecode]

> William P. wrote:
> I use:
> on mouseUp
> set the cursor to # —the ID of the image
> lock cursor
> end mouseUp 

You could try to _first_ lock the cursor then set it.
(This works for here).
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Setting the Cursor to an image

[William Prothero via use-livecode]

I submitted a bug report (bug #: 19092) for this.
Best,
Bill

> On Jan 11, 2017, at 3:46 PM, William Prothero via use-livecode 
>  wrote:
> 
> Folks:
> I am setting the cursor to a 32x32 image. It works in the standalone app, but 
> not in the development system. Is there something wrong with the IDE?
> 
> This happens in version 8 and 9 (latest downloads).
> 
> I use:
> 
> on mouseUp
>set the cursor to #—the ID of the image
>lock cursor
> end mouseUp
> 
> What’s up? I’d like to have this work in the IDE.
> 
> Best,
> Bill
> 
> William A. Prothero
> http://earthlearningsolution.org/
> 
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Documentation on Dispatch

[Sannyasin Brahmanathaswami via use-livecode]

@ pass by reference

Wow! I'm only now learning about this? ….sheesh, this would have solved so many 
issues I faced in the past!

and now pass arrays too. Fantastic.

@ Richard: yes "wrap" was the wrong way to state this… "call a function with 
dispatch" is was I should have said

BR

PS there is also some convention for using   

[var]  # value inside square braces… 

 that I see in some scripts… what is that about? A custom thing? or is this 
also some jewel expression like @ that you will never learn about unless you 
fall onto it?






 

On 1/10/17, 1:54 PM, "use-livecode on behalf of Bleiler, Timothy via 
use-livecode"  wrote:

e variables passed as call by reference can also be arrays, 

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: I need help with UTF-8

[Kay C Lan via use-livecode]

We may need to see your actual scripts to determine where the problem
may  be. Also, how do you know that your MySQL db data is corrupt?
What program are you using to look at it? How was the db set up in the
first place; what character set and collation? Is it possible that
your Windows db Client is set to UTF8 whilst your Mac db Client is set
to MacRoman?

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: [ANN] Important: reply before friday - conference!

[Dirk prive via use-livecode]

I might go, but it really depends on when. If it's on Saturday I'll be able
to join.

On Jan 12, 2017 22:41, "Mark Schonewille via use-livecode" <
use-livecode@lists.runrev.com> wrote:

> We really need 4 or 5 more participants to make the conference possible.
> If you are planning to go, let me know! If you know someone else who might
> go, ask him or her to send me a message.
>
> Kind regards,
>
> Mark Schonewille
> http://economy-x-talk.com
> https://www.facebook.com/marksch
>
> Buy the most extensive book on the
> LiveCode language:
> http://livecodebeginner.economy-x-talk.com
>
> Op 12-Jan-17 om 00:42 schreef Mark Schonewille:
>
>> International LiveCode Mini Conference
>>
>> - Time and date are still preliminary!
>> - Make sure to send a message to me on Friday or earlier if you're
>> interested!
>> - decisions are made over the weekend, depending on feedback!
>>
>> In the second half of February, an international LiveCode Mini
>> Conference has been scheduled. The dates are still to be determined. The
>> conference has been planned to take place during the weekends of 18 or
>> 25 February.
>>
>> PLEASE NOTE: While the conference is called a "LiveCode" conference,
>> anyone with an interest in rapid application development is invited:
>> database admins, Filemaker users, Xojo fans, SuperCard aficionados, and
>> anyone who is looking for new ways to be creative with computers.
>>
>> All information is preliminary. As the date of the conference
>> approaches, we will have all information available.
>>
>> The conference will consist of one day with multiple sessions. We're
>> planning simultaneous workshops and presentations. We're thinking of
>> four times two simultaneous sessions of 30 minutes. Afterwards, there
>> will be plenty of opportunity to meet with fellow programmers and
>> discuss any topic you like.
>>
>> The conference will be held in Antwerp, Belgium, to facilitate
>> participation by British, French and German people. Obviously, you're
>> also invited if you live in a different country.
>>
>> We're planning to rent a conference room. Therefore, there will be a
>> small fee of approximately 35 euro (including VAT, with invoice).  If
>> you want to host a workshop or give a presentation, you'll be eligible
>> for a discount. Since fees are small, discounts will be small too.
>>
>> Possible topics:
>> - Getting started with LiveCode
>> - Advanced LiveCode scripting
>> - Widgets
>> - Arduino and Raspberry Pi
>> - Usage in real life (home and business)
>> - DBMS (MySQL, PostGreSQL, XML, others)
>> - FileMaker
>> - SuperCard
>> - HyperStudio
>> - Xojo
>> - PHP
>> - other subjects
>>
>> You might want to spend one or two nights in a hotel. We'll be happy to
>> help you find board and lodgings. The hotel room, drinks, food and other
>> expenses will be on your own account.
>>
>> We would like to know how many people are interested. Please, send a
>> reply to support (at) economy-x-talk.com before Friday 13th if you're
>> interested. This weekend, all decisions will be made final.
>>
>> This might be the only edition of this conference! Grab the opportunity
>> and make sure you're there! It is going to be special for sure!
>>
>>
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

RE: Android Keyboard Activation Issue

[Andrew Bell via use-livecode]

Not sure why yours would be working different. I abbreviated much of  
my card script for list purposes, but I actually create 2  
mobileControl objects that appear right after each other on the card  
using nearly identical code: inputCreateTSM and inputCreateEmail are  
both called from preOpenScript. inputCreateTSM has the focus as it  
appears first visually.


I also seem to have some legacy code (commented out) for  
"onInputFocus" that I likely got from here but don't know how it (or  
if) it even does anything:  
http://lessons.livecode.com/m/4069/l/29112-how-do-i-use-native-text-controls-on-mobile


on inputFocus
# set the focus to the native text input
mobileControlDo "TSMinput", "focus"
end inputFocus

--Andrew Bell


--

Message: 9
Date: Thu, 12 Jan 2017 11:41:07 -0600
From: "Livecode XAC" 
To: "'How to use LiveCode'" 
Subject: RE: Android Keyboard Activation Issue
Message-ID: <03CD51D6F3F24623868445DE2D2AF03D@NetCentral>
Content-Type: text/plain;   charset="us-ascii"

Andrew,

I'm doing the same type of thing, but because I have multiple input fields
on the card, I send the inputCreateTSM when the user selects the field.

Here is the function that I'm using to create the Native Control when the
field is selected.


on inputCreatorWide pName, pFld, pContent, pKeyboardType, pAutoCap,
pAutoCorrect, pReturn, pDataDetect

   if environment() is not "mobile" then exit inputCreatorWide

   put the uOS of this stack into tOsType

   if tOsType = "android" then
  get inputCleanUp()
   end if

   if pFld contains "stack" then   -- removed the stack part of the field
identifier
  put wordOffset("stack",pFld) into tWord
  put word 1 to (tWord -2) of pFld into pFld
   end if

   get setInputFieldName( pFld )  -- Save the active Input Field

   get moveToVisibleArea( pFld )-- Make sure the field is within the
visible area of the display.

   put the rect of pFld into tSize
   put the height of pFld into tHeight
   put the width of pFld into tWidth

   if tOsType = "android" then
  set the itemdel to ","
  add (tHeight/2) to item 4 of tSize -- Increase the field size
  if tWidth < 50 then
 add (100 - tWidth) to item 3 of tSize
  end if
   end if

   mobileControlCreate "input", pName
   mobileControlSet pName, "rect", tSize -- standard for all controls
   mobileControlSet pName, "visible", "True"  -- standard for all controls
   mobileControlSet pName, "text", pContent

   if tOsType = "ios" then
  mobileControlSet pName, "alpha", "255"
  mobileControlSet pName, "backgroundColor", "240,248,255,255"
   end if

   -- Font Size
   if tHeight >60 then
 mobileControlSet pName, "fontSize", 20
  else if tHeight > 50 AND tHeight <= 60 then
 mobileControlSet pName, "fontSize", 21
  else if tHeight > 40 AND tHeight <= 50 then
 mobileControlSet pName, "fontSize", 17
  else
 mobileControlSet pName, "fontSize", 14
  end if

   mobileControlSet pName, "textAlign", "left"

   if pKeyboardType is not Empty then
  if tOsType = "ios" AND pKeyboardType = "number" OR pKeyboardType =
"numeric" then
 mobileControlSet pName, "keyboardType", "numeric"
  else
 mobileControlSet pName, "keyboardType", pKeyboardType
  end if
   else
  mobileControlSet pName, "keyboardType", "default"
   end if

   if pReturn is not Empty then
  mobileControlSet pName, "returnKeyType", pReturn
   else
  mobileControlSet pName, "returnKeyType", "default"
   end if

   if pAutoCap is not Empty then
  mobileControlSet pName, "autoCapitalizationType", pAutoCap
   else
  mobileControlSet pName, "autoCapitalizationType", "none"
   end if

   if pAutoCorrect is not Empty then
  mobileControlSet pName, "autoCorrectionType", pAutoCorrect
   else
  mobileControlSet pName, "autoCorrectionType", "default"
   end if

   -- Set the field parameters for iOS

   if tOsType = "ios" then
  mobileControlSet pName, "font", "arial"
  mobileControlSet pName, "autoFit", true
  mobileControlSet pName, "minimumFontSize", "14"
  mobileControlSet pName, "autoClear", false
  mobileControlSet pName, "borderStyle", "line"
  mobileControlSet pName, "manageReturnKey", false
  mobileControlSet pName, "keyboardStyle", "default"
  mobileControlSet pName, "clearButtonMode", "unless editing"
   end if

   -- Focus on the Control
   mobileControlDo pName, "focus" -- actually focus on the field
so the keyboard pops up

end inputCreatorWide


Mine is more complex, but for some reason it will not bring up the Keyboard
on Android, but does on iOS.
Is the same behavior you are seeing?

Thanks for the response
Dan

-Original Message-
From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf
Of Andrew Bell via use-livecode
Sent: Thursday, January 12, 2017 10:48 AM
To: 

RE: Android Keyboard Activation Issue

[Livecode XAC via use-livecode]

Dave,

Thank you for your response.  I'm not using multi-line text box, so that is
not an issue.

I'm currently using this command in the OpenCard to activate the field:
send "touchStart" to fld "ExerValue" on this card in 100 milliseconds 

This creates the native text input box, but doesn't bring up the keyboard.
The color of the text box changes to the color defined in the native text
box, but when you touch it a second time Android puts a orange highlight on
the text box and brings up the keyboard.  So it goes from the field not
being focused to having focus.

I also added the on keyboardDeactivated handler to the card, but that didn't
resolve the issue.

I also tried put the following in the Native Text Box Create handler.
   if tOsType = "android" then
  send "touchStart" to me in 300 milliseconds
   end if

This just resulted in the field blinking on and off and the keyboard never
coming up.  I think it was creating the Native control handler over and
over.  I need a way to send focus to the Native Control.  I have the
following at the end of my create function.

  mobileControlDo pName, "focus" -- pName is the passed name of
the control

This doesn't do anything in Android.

Any other suggestions??

Thanks
Dan


   


-Original Message-
From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf
Of Dave Kilroy via use-livecode
Sent: Thursday, January 12, 2017 12:21 PM
To: use-revolut...@lists.runrev.com
Cc: Dave Kilroy
Subject: Re: Android Keyboard Activation Issue

Hi Dan - is your native control multi-line? If so the dictionary says
mobileControlDo multi-line text input specific actions are for iOS only.

I use a 'send' command to create native controls in the openCard handler in
500ms which works in iOS and Android. When I have more than on native input
on a card I make use of: inputFocus, mobileControlTarget, inputBeginEditing
etc.

Also I've had a problem with getting the keyboard to slide out on Android
without an extra tap so I use the following in the keyboardDeactivated
message

 if isAndroid() then
  focus on fld "fldInput1"
  focus on nothing
 end if

So it just may be that if you check exactly where the focus is before the
keyboard appears that you can cut out your extra tap...



-
"The first 90% of the task takes 90% of the time, and the last 10% takes the
other 90% of the time."
Peter M. Brigham
--
View this message in context:
http://runtime-revolution.278305.n4.nabble.com/Android-Keyboard-Activation-I
ssue-tp4711601p4711612.html
Sent from the Revolution - User mailing list archive at Nabble.com.

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Array Properties in a Standalone

[Mark Talluto via use-livecode]

> On Jan 12, 2017, at 2:15 PM, Bob Sneidar via use-livecode 
>  wrote:
> 
> Thanks for the assistance, and if any of the dev team thinks this is not how 
> a standalone can work, contact me offline as you please, an I will be glad to 
> assist. The standalone is too big to send via the QC uploads however, and I 
> would have to create a login for you in the database for you to actually see 
> it running. I don't mind doing that but we would have to arrange that off 
> list.
> 
> Bob S

Hi Bob,

Writing to stacks in your bundle will work if you do not need the app to be 
code-signed. If the app is to be distributed via the Apple Store or you just 
wanted your app code-signed to prevent GateKeeper showing up, you will need to 
write to files outside of the app bundle.

Best regards,

Mark Talluto
livecloud.io
canelasoftware.com




___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Array Properties in a Standalone

[Bob Sneidar via use-livecode]

Hi Jacque.

As I mentioned, I created a custom property called pIncrement. Each time I 
launch the app, I increment this property by 1 then write it out to a log file. 
The log file indicates that the property IS getting written to and saved. I 
understand that I cannot write to an executable file, of course. That is why I 
have a splash stack that I compile everything from. THAT becomes the executable 
inside the "app bundle" or "Package" from which I launch Forms Generator and 
all the magic happens.

This is how I always thought it would work and indeed, it seems it does. (Big 
sigh of relief). However, the Forms Generator stack still shows 0k size, and 
yet the app still works a peach! I checked prior compiled apps I had zipped up 
and saved, and the Forms Generator stack was of some significant file size 
inside the package. Not sure what this means.

I suppose it's all academic, as the app DOES work as advertised, only I cannot 
use "the mainstack of" inside a standalone (I wonder what else does not work in 
a standalone as it does in the IDE??) But I have worked around that one anyway.

Thanks for the assistance, and if any of the dev team thinks this is not how a 
standalone can work, contact me offline as you please, an I will be glad to 
assist. The standalone is too big to send via the QC uploads however, and I 
would have to create a login for you in the database for you to actually see it 
running. I don't mind doing that but we would have to arrange that off list.

Bob S


On Jan 12, 2017, at 12:13 , J. Landman Gay via use-livecode 
> wrote:

In either case, you can't write to the app bundle.

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Array Properties in a Standalone

[Bob Sneidar via use-livecode]

I mean the checkbox "Move Substacks into individual stack files" is UNCHECKED 
and the stacks are NOT substacks of the original stack. When I open the package 
(OS X), I see that in the MacOS folder there is an executalbe file called Forms 
Generator (which is what I told the splash stack the app was called so that 
makes sense). In the Resources/_MacOS folder I see eack substack as an 
individual file with the extension set to .rev. The Forms Generator stack (the 
original mainstack but NOT the splash stack) has the extension .livecode. So do 
the included libraries. Curiously, the Forms Generator stack is 0 bytes big! 
The other stacks are of some size.

When you say the stacks cannot be modified, that may be however I see that I 
have read/write permissions to the substacks (the customers.rev for example). I 
was also successful in copying a file to the folder the substacks are in. Mind 
you these are folders IN the application package.

Also if I cannot modify one of these substacks then properties as a means to 
save persistent values between launches is a complete bust! I make extensive 
use of this. I really do not want to have to write this data out to a file 
because some of it is values I do not want the user to gain access to. At least 
not easily.

I am going to test this and let you know. I am going to increment a numeric 
property in the customers stack and pop a dialog each time I launch it 
displaying the value.

Bob S


On Jan 12, 2017, at 12:13 , J. Landman Gay via use-livecode 
> wrote:

On 1/12/17 12:25 PM, Bob Sneidar via use-livecode wrote:
Even though in the standalone settings I have the option to save
substacks as individual stacks unchecked, it does it anyway. It just
puts them in the app package instead of in another folder.

Did you mean "checked"? If checked, that option will extract substacks and save 
them as independent mainstacks. If not checked, they remain substacks. If LC 
isn't behaving that way it's a bug.

In either case, you can't write to the app bundle. If you want to save data, 
you need to copy the stacks to a writable location on first launch. The 
standalone builder can't know where you will want to save those stacks, and 
always places them into a folder you can access with 
specialFolderPath("resources").

--
Jacqueline Landman Gay | 
jac...@hyperactivesw.com

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: [ANN] Important: reply before friday - conference!

[Mark Schonewille via use-livecode]

We really need 4 or 5 more participants to make the conference possible. 
If you are planning to go, let me know! If you know someone else who 
might go, ask him or her to send me a message.


Kind regards,

Mark Schonewille
http://economy-x-talk.com
https://www.facebook.com/marksch

Buy the most extensive book on the
LiveCode language:
http://livecodebeginner.economy-x-talk.com

Op 12-Jan-17 om 00:42 schreef Mark Schonewille:

International LiveCode Mini Conference

- Time and date are still preliminary!
- Make sure to send a message to me on Friday or earlier if you're
interested!
- decisions are made over the weekend, depending on feedback!

In the second half of February, an international LiveCode Mini
Conference has been scheduled. The dates are still to be determined. The
conference has been planned to take place during the weekends of 18 or
25 February.

PLEASE NOTE: While the conference is called a "LiveCode" conference,
anyone with an interest in rapid application development is invited:
database admins, Filemaker users, Xojo fans, SuperCard aficionados, and
anyone who is looking for new ways to be creative with computers.

All information is preliminary. As the date of the conference
approaches, we will have all information available.

The conference will consist of one day with multiple sessions. We're
planning simultaneous workshops and presentations. We're thinking of
four times two simultaneous sessions of 30 minutes. Afterwards, there
will be plenty of opportunity to meet with fellow programmers and
discuss any topic you like.

The conference will be held in Antwerp, Belgium, to facilitate
participation by British, French and German people. Obviously, you're
also invited if you live in a different country.

We're planning to rent a conference room. Therefore, there will be a
small fee of approximately 35 euro (including VAT, with invoice).  If
you want to host a workshop or give a presentation, you'll be eligible
for a discount. Since fees are small, discounts will be small too.

Possible topics:
- Getting started with LiveCode
- Advanced LiveCode scripting
- Widgets
- Arduino and Raspberry Pi
- Usage in real life (home and business)
- DBMS (MySQL, PostGreSQL, XML, others)
- FileMaker
- SuperCard
- HyperStudio
- Xojo
- PHP
- other subjects

You might want to spend one or two nights in a hotel. We'll be happy to
help you find board and lodgings. The hotel room, drinks, food and other
expenses will be on your own account.

We would like to know how many people are interested. Please, send a
reply to support (at) economy-x-talk.com before Friday 13th if you're
interested. This weekend, all decisions will be made final.

This might be the only edition of this conference! Grab the opportunity
and make sure you're there! It is going to be special for sure!



___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Array Properties in a Standalone

[J. Landman Gay via use-livecode]

On 1/12/17 12:25 PM, Bob Sneidar via use-livecode wrote:

Even though in the standalone settings I have the option to save
substacks as individual stacks unchecked, it does it anyway. It just
puts them in the app package instead of in another folder.


Did you mean "checked"? If checked, that option will extract substacks 
and save them as independent mainstacks. If not checked, they remain 
substacks. If LC isn't behaving that way it's a bug.


In either case, you can't write to the app bundle. If you want to save 
data, you need to copy the stacks to a writable location on first 
launch. The standalone builder can't know where you will want to save 
those stacks, and always places them into a folder you can access with 
specialFolderPath("resources").


--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Array Properties in a Standalone

[Bob Sneidar via use-livecode]

Thanks all.

What I did was put a function in the backscript script called homestack(), 
which simply returns the name of what ought to be the Main Stack (but isn't 
anymore in a standalone). I think anyone who wants to start saving as 
standalones should be alerted to this little quirk. Even though in the 
standalone settings I have the option to save substacks as individual stacks 
unchecked, it does it anyway. It just puts them in the app package instead of 
in another folder.

I suppose I should be using the latter method as that would allow me to much 
more easily update a particular stack without redistributing the whole app all 
over again. Something to think about.

Bob S


On Jan 11, 2017, at 18:43 , Mark Wieder via use-livecode 
> wrote:

On 01/11/2017 04:30 PM, Bob Sneidar via use-livecode wrote:
I read in the dictionary:

If you place the constant statement in a handler, you can use the constant 
anywhere in the handler. If you place the constant statement in a script 
outside any handler, you can use the constant anywhere in the handlers of that 
script.

Any way to declare a global constant? I think I know the answer, but I thought 
I'd ask.

Heh.
There are requests for this in the bug database going back to 2004.

To make matters worse, if you're really diabolical you could declare different 
values for constants in different scripts.

script 1:
constant onePlusOne = 2

script 2:
constant onePlusOne = 3

--
Mark Wieder
ahsoftw...@gmail.com

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Android Keyboard Activation Issue

[Dave Kilroy via use-livecode]

Hi Dan - is your native control multi-line? If so the dictionary says
mobileControlDo multi-line text input specific actions are for iOS only.

I use a 'send' command to create native controls in the openCard handler in
500ms which works in iOS and Android. When I have more than on native input
on a card I make use of: inputFocus, mobileControlTarget, inputBeginEditing
etc.

Also I've had a problem with getting the keyboard to slide out on Android
without an extra tap so I use the following in the keyboardDeactivated
message

 if isAndroid() then
  focus on fld "fldInput1"
  focus on nothing
 end if

So it just may be that if you check exactly where the focus is before the
keyboard appears that you can cut out your extra tap...



-
"The first 90% of the task takes 90% of the time, and the last 10% takes the 
other 90% of the time."
Peter M. Brigham 
--
View this message in context: 
http://runtime-revolution.278305.n4.nabble.com/Android-Keyboard-Activation-Issue-tp4711601p4711612.html
Sent from the Revolution - User mailing list archive at Nabble.com.

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

RE: Android Keyboard Activation Issue

[Livecode XAC via use-livecode]

Andrew,

I'm doing the same type of thing, but because I have multiple input fields
on the card, I send the inputCreateTSM when the user selects the field.

Here is the function that I'm using to create the Native Control when the
field is selected.


on inputCreatorWide pName, pFld, pContent, pKeyboardType, pAutoCap,
pAutoCorrect, pReturn, pDataDetect
   
   if environment() is not "mobile" then exit inputCreatorWide
   
   put the uOS of this stack into tOsType
   
   if tOsType = "android" then
  get inputCleanUp()
   end if
  
   if pFld contains "stack" then   -- removed the stack part of the field
identifier
  put wordOffset("stack",pFld) into tWord
  put word 1 to (tWord -2) of pFld into pFld
   end if
   
   get setInputFieldName( pFld )  -- Save the active Input Field
   
   get moveToVisibleArea( pFld )-- Make sure the field is within the
visible area of the display.

   put the rect of pFld into tSize   
   put the height of pFld into tHeight
   put the width of pFld into tWidth
   
   if tOsType = "android" then
  set the itemdel to ","
  add (tHeight/2) to item 4 of tSize -- Increase the field size
  if tWidth < 50 then
 add (100 - tWidth) to item 3 of tSize
  end if
   end if
   
   mobileControlCreate "input", pName
   mobileControlSet pName, "rect", tSize -- standard for all controls
   mobileControlSet pName, "visible", "True"  -- standard for all controls
   mobileControlSet pName, "text", pContent
   
   if tOsType = "ios" then
  mobileControlSet pName, "alpha", "255"
  mobileControlSet pName, "backgroundColor", "240,248,255,255"
   end if
   
   -- Font Size
   if tHeight >60 then
 mobileControlSet pName, "fontSize", 20
  else if tHeight > 50 AND tHeight <= 60 then
 mobileControlSet pName, "fontSize", 21
  else if tHeight > 40 AND tHeight <= 50 then
 mobileControlSet pName, "fontSize", 17
  else
 mobileControlSet pName, "fontSize", 14
  end if
   
   mobileControlSet pName, "textAlign", "left"
   
   if pKeyboardType is not Empty then 
  if tOsType = "ios" AND pKeyboardType = "number" OR pKeyboardType =
"numeric" then
 mobileControlSet pName, "keyboardType", "numeric"
  else
 mobileControlSet pName, "keyboardType", pKeyboardType
  end if 
   else
  mobileControlSet pName, "keyboardType", "default"
   end if
   
   if pReturn is not Empty then 
  mobileControlSet pName, "returnKeyType", pReturn
   else
  mobileControlSet pName, "returnKeyType", "default"
   end if
   
   if pAutoCap is not Empty then 
  mobileControlSet pName, "autoCapitalizationType", pAutoCap
   else
  mobileControlSet pName, "autoCapitalizationType", "none"
   end if
   
   if pAutoCorrect is not Empty then 
  mobileControlSet pName, "autoCorrectionType", pAutoCorrect
   else
  mobileControlSet pName, "autoCorrectionType", "default"
   end if
  
   -- Set the field parameters for iOS
   
   if tOsType = "ios" then
  mobileControlSet pName, "font", "arial"
  mobileControlSet pName, "autoFit", true
  mobileControlSet pName, "minimumFontSize", "14"
  mobileControlSet pName, "autoClear", false
  mobileControlSet pName, "borderStyle", "line"
  mobileControlSet pName, "manageReturnKey", false
  mobileControlSet pName, "keyboardStyle", "default"
  mobileControlSet pName, "clearButtonMode", "unless editing"
   end if
  
   -- Focus on the Control
   mobileControlDo pName, "focus" -- actually focus on the field
so the keyboard pops up
   
end inputCreatorWide


Mine is more complex, but for some reason it will not bring up the Keyboard
on Android, but does on iOS.
Is the same behavior you are seeing?

Thanks for the response
Dan

-Original Message-
From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf
Of Andrew Bell via use-livecode
Sent: Thursday, January 12, 2017 10:48 AM
To: use-livecode@lists.runrev.com
Cc: and...@midwestcoastmedia.com
Subject: Re: Android Keyboard Activation Issue

Here is a card script I'm currently using that seems to work in an
iOS/Android app I have now:

on preOpenCard
   inputCreateTsm
end preOpenCard

on inputCreateTSM
put the rect of graphic "tsmRectangle" into tThisRect
# do some math to visually accommodate a roundedRect with innerShadow
add 15 to item 1 of tThisRect
subtract 10 from item 3 of tThisRect
mobileControlCreate "input", "TSMinput"
mobileControlSet "TSMinput", "rect", tThisRect
mobileControlSet "TSMinput", "text", line 1 of gCurrentPrefs
mobileControlSet "TSMinput", "keyboardType", "number"
mobileControlSet "TSMinput", "fontSize", 21
mobileControlSet "TSMinput", "fontName", "Roboto Light" -- iOS only
mobileControlSet "TSMinput", "textAlign", "center"
mobileControlSet "TSMinput", "visible", true
# make sure the field has focus, which activates the keyboard
mobileControlDo 

Re: Help: Odd menu behavior under LC6.7.11 on OSX

[J. Landman Gay via use-livecode]

For the text issue you can set the theme of the stack to "legacy" and it 
will use the old settings.


What bug are you seeing?
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com



On January 12, 2017 5:43:08 AM Roger Eller via use-livecode 
 wrote:



6.7.5 is my poison of choice.  8.x gives an error when it opens.  Bug was
reported several times, but it's still there, even in the latest.  Also, my
Windows applications are tightly spaced in the UI department, and 8.x text
spacing goes crazy. It would take a lot of time to go through everything
and adjust the text spacing.

~Roger

On Jan 12, 2017 3:16 AM, "Richmond Mathewson via use-livecode" <
use-livecode@lists.runrev.com> wrote:


If you want to talk about a "perv": I'm currently using 7.1.4 for all my
development work.

Richmond.

On 1/12/17 12:02 am, Curry Kenworthy via use-livecode wrote:



Richmond:
> Well, the first question anyone is going to ask is why
> on earth you are using 6.7.11?

Don't forget to use "OMG/LOL/derisno/perv" as in for example: "OMG, why
are you using 6.7, are you a total perv? Derisno past! LOL." :)

There is a history to every product, and not only do we learn a lot by
comparing past to present, but the latest version of LC that people take
for granted owes a lot of fixes and some features to Paul in particular due
to his meticulous work and testing, providing a huge benefit to the entire
community!

It's wonderful to keep up with recent LC releases, especially where Apple
is concerned, but sometimes circumstances and LC bugs/features can affect
the speed of that process. Then you have people who grab the latest DP,
precisely because it is the very latest thing, and get confused trying to
tell the difference between their own bugs and DP bugs. I help people with
that often enough to know that a chorus of "just grab the latest" is advice
that needs clarification.

Paul:
> We are seeing a weird menu rendering issues under OSX

I believe this menu issue is also a current bug in LC 8.1.2! Haven't
tried it yet in LC 9, but I will soon. LC 6.6 was okay, so it must have
been introduced in 6.7 and remained until now.

Craig:
> I am hunkered down in v6 until I can swallow the new "look"
> of v8/9. The only thing I really miss from those is the new
> multi-char itemDelimiter.

Change for the sake of change keeps some people incredibly happy, others
less so! The new interface does take some getting used to, and the old
interface definitely had its strengths too, as I've realized lately with
certain particular tasks and with teaching others. Much to learn from
comparing and critiquing LC versions, enjoying the very latest as well as
some past specimens!

Best wishes,

Curry Kenworthy

Custom Software Development
http://livecodeconsulting.com/


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode



___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your 
subscription preferences:

http://lists.runrev.com/mailman/listinfo/use-livecode




___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: [OT] Download Request

[Andrew Bell via use-livecode]

Date: Wed, 11 Jan 2017 14:25:21 -0600
From: Randy Hengst 
To: How to use LiveCode 
Subject: Re: [OT] Download Request
Message-ID: <2123c29c-82dc-49ec-915c-86ae74918...@mac.com>
Content-Type: text/plain;   charset=utf-8

A quick follow-up? the initial response from Apple said that they?d  
get back to me within 3 business days? actually, they responded in 6  
hours with a fix? so, all is well.


Apple really has gotten faster and the review process? this one for  
me only took two days.


Apple review has gotten WAY faster in the two years I've been using  
LiveCode! There are still some slow periods, but they seem to be  
historically predictable (it's about to go up a few days on average  
for the next few weeks). When I'm planning a timeline for a project, I  
always glance at http://appreviewtimes.com/ to get an idea of how long  
to account for approval (then double it because I seem to get the most  
random rejections depending on the reviewer).


As opposed to Android builds that I can get a bug notice in an  
overnight client email, hot fix after breakfast, and have available  
publicly by lunch that same day. Sometimes I fix a bug and push out  
the new build before I even reply to the client so I can just be like,  
"Yeah, I fixed that already."


--Andrew Bell


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Android Keyboard Activation Issue

[Andrew Bell via use-livecode]

Here is a card script I'm currently using that seems to work in an  
iOS/Android app I have now:


on preOpenCard
  inputCreateTsm
end preOpenCard

on inputCreateTSM
   put the rect of graphic "tsmRectangle" into tThisRect
   # do some math to visually accommodate a roundedRect with innerShadow
   add 15 to item 1 of tThisRect
   subtract 10 from item 3 of tThisRect
   mobileControlCreate "input", "TSMinput"
   mobileControlSet "TSMinput", "rect", tThisRect
   mobileControlSet "TSMinput", "text", line 1 of gCurrentPrefs
   mobileControlSet "TSMinput", "keyboardType", "number"
   mobileControlSet "TSMinput", "fontSize", 21
   mobileControlSet "TSMinput", "fontName", "Roboto Light" -- iOS only
   mobileControlSet "TSMinput", "textAlign", "center"
   mobileControlSet "TSMinput", "visible", true
   # make sure the field has focus, which activates the keyboard
   mobileControlDo "TSMinput", "focus"
end inputCreateTSM


on closeCard
   # delete the native text input
   mobileControlDelete "TSMinput"
end closeCard




Date: Thu, 12 Jan 2017 03:44:19 +
From: "Daniel Pierce" 
To: "'Daniel Pierce via use-livecode'" 
Subject: Android Keyboard Activation Issue
Message-ID:

<0101015990c6b871-5fd4abdc-5e55-49b8-9a80-9c172ffe6fee-000...@us-west-2.amazonses.com>

Content-Type: text/plain;   charset="us-ascii"

List,

I have developed a cross platform mobile app for iOS and Android using
LiveCode and it is working OK, but I continue to get a common complaint from
Android users that when they select a field the keyboard does not activate
like on other apps.

This is not an issue on iOS because a when you create the Native Text Box,
you can send the command mobileControlDo  "focus" and the keyboard is
activated with a single touch to the text entry field.

Android doesn't support this capability so the users needs to touch the
field to activate the Native Text Box and then touch it again to bring up
the keyboard.

Has anyone found a way to bring up the virtual keyboard when the Native Text
Box has been created

Thanks for your advice.
Dan




___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: [OT] KOUSEK (or replacement) code snippet manager replacement?

[Lagi Pittas via use-livecode]

Hi

I used Quiver 3

Allows you to sync to dropbox , google drive etc, export as pdf,, html,
markdown, plain text and json (infact the actual data is json)

What I love is I can cut and paste websites and all the graphics and
formatting are stored as well and the syntax coloring for most of the
languages I use (except livecode ;-( ) in fact its because it included the
ace text editor in "cells".

And if you are that way inclined it will do latex.

And for $9.99 it isnt even worth thinking about a trial

http://happenapps.com/

Lagi





On 12 January 2017 at 01:12, Stephen Barncard via use-livecode <
use-livecode@lists.runrev.com> wrote:

> I have been using KOUSEK for years. It (was) a simple, easy to use code
> snippet manager I started using about 5 years ago after I couldn't manage
> Rev-based manager that dropped out of sight. Now Kousek has irresponsibly
> dropped out of sight too, but my snippets remain. The app wants credentials
> that I don't have - it was paid for and downloaded from the apple app
> store.
>
> The exported data appears to be XML based and logically arranged, but I'd
> rather not have to re-create it.
>
> Has anyone else  here used this app and found a replacement? I'd rather not
> use GIT if I don't have to. Or perhaps found an app that could convert the
> data into tab-delimited data?
>
> thanks for any and all advice.
>
> sqb
> --
> Stephen Barncard - Sebastopol Ca. USA -
> mixstream.org
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Re [OT] Download Request

[Randy Hengst via use-livecode]

Thank you for letting me know. I’ve now seen it on the US store.

be well,
randy


> On Jan 12, 2017, at 7:01 AM, David Milne via use-livecode 
>  wrote:
> 
> Hi Randy,
> 
> Number Tile Fill Up
> I picked up your software in the New Zealand store at 1.58 am Friday 13
> (New Zealand Local time and date)
> 
> Regards
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

I need help with UTF-8

[Tiemo Hollmann TB via use-livecode]

Hello,

 

I am migrating a LC 6 program to LC 8 and shortly before release, after I
thought I have made all hurdles I am again lost with Mac - LC 8 - PHP -
MySQL -UTF-8 and German Umlaute (the MySQL name field is "utf8_general_ci"
coded):

Scenario 1 (without local file):

-  Entering a name with Umlaute in LC: ok

-  Checking the name in LC: ok

-  Passing the name to PHP and writing it to a MySQL db: ok

This works fine, without any changes in LC 6 and LC 8

 

Scenario 2 (with local file, without textencode):

-  Entering a name with Umlaute in LC: ok

-  Writing it to a local file

-  Reading it from a local file

-  Checking the name in LC: ok

-  Passing the name to PHP and writing it to a MySQL db: corrupted

This works fine in LC 6 on Win and Mac. In LC 8 on Windows it is also ok,
but running the program on MacOS 10.12, the Umlaute enter the MySQL database
corrupted.

 

Scenario 3 (textEncode before passing to PHP):

-  Entering a name with Umlaute in LC

-  Writing it to a local file

-  Reading it from a local file

-  textEncode() the content for the file: coruppted

-  Passing the name to PHP and writing it to a MySQL db: coruppted

 

Scenario 4 (textEncode/Decode for local file and PHP):

-  Entering a name with Umlaute in LC

-  textEncode() the content for the file: coruppted

-  Writing it to a local file

-  Reading it from a local file

-  textDecode() the content from the file: corrupted

-  Alternativily additional: textEncode() the content from the file:
corrupted

-  Passing the name to PHP and writing it to a MySQL db: coruppted

 

It seems that I still havn't understood UTF-8 handling in LC

Where is my fault? And why is it working on Windows and not on Mac?

Thanks for any help!

Tiemo

 

 

 

 

 

 

 

 

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re [OT] Download Request

[David Milne via use-livecode]

Hi Randy,

Number Tile Fill Up
I picked up your software in the New Zealand store at 1.58 am Friday 13
(New Zealand Local time and date)

Regards
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Help: Odd menu behavior under LC6.7.11 on OSX

[Roger Eller via use-livecode]

6.7.5 is my poison of choice.  8.x gives an error when it opens.  Bug was
reported several times, but it's still there, even in the latest.  Also, my
Windows applications are tightly spaced in the UI department, and 8.x text
spacing goes crazy. It would take a lot of time to go through everything
and adjust the text spacing.

~Roger

On Jan 12, 2017 3:16 AM, "Richmond Mathewson via use-livecode" <
use-livecode@lists.runrev.com> wrote:

> If you want to talk about a "perv": I'm currently using 7.1.4 for all my
> development work.
>
> Richmond.
>
> On 1/12/17 12:02 am, Curry Kenworthy via use-livecode wrote:
>
>>
>> Richmond:
>> > Well, the first question anyone is going to ask is why
>> > on earth you are using 6.7.11?
>>
>> Don't forget to use "OMG/LOL/derisno/perv" as in for example: "OMG, why
>> are you using 6.7, are you a total perv? Derisno past! LOL." :)
>>
>> There is a history to every product, and not only do we learn a lot by
>> comparing past to present, but the latest version of LC that people take
>> for granted owes a lot of fixes and some features to Paul in particular due
>> to his meticulous work and testing, providing a huge benefit to the entire
>> community!
>>
>> It's wonderful to keep up with recent LC releases, especially where Apple
>> is concerned, but sometimes circumstances and LC bugs/features can affect
>> the speed of that process. Then you have people who grab the latest DP,
>> precisely because it is the very latest thing, and get confused trying to
>> tell the difference between their own bugs and DP bugs. I help people with
>> that often enough to know that a chorus of "just grab the latest" is advice
>> that needs clarification.
>>
>> Paul:
>> > We are seeing a weird menu rendering issues under OSX
>>
>> I believe this menu issue is also a current bug in LC 8.1.2! Haven't
>> tried it yet in LC 9, but I will soon. LC 6.6 was okay, so it must have
>> been introduced in 6.7 and remained until now.
>>
>> Craig:
>> > I am hunkered down in v6 until I can swallow the new "look"
>> > of v8/9. The only thing I really miss from those is the new
>> > multi-char itemDelimiter.
>>
>> Change for the sake of change keeps some people incredibly happy, others
>> less so! The new interface does take some getting used to, and the old
>> interface definitely had its strengths too, as I've realized lately with
>> certain particular tasks and with teaching others. Much to learn from
>> comparing and critiquing LC versions, enjoying the very latest as well as
>> some past specimens!
>>
>> Best wishes,
>>
>> Curry Kenworthy
>>
>> Custom Software Development
>> http://livecodeconsulting.com/
>>
>>
>> ___
>> use-livecode mailing list
>> use-livecode@lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
>>
>
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Help: Odd menu behavior under LC6.7.11 on OSX

[Richmond Mathewson via use-livecode]

If you want to talk about a "perv": I'm currently using 7.1.4 for all my 
development work.


Richmond.

On 1/12/17 12:02 am, Curry Kenworthy via use-livecode wrote:


Richmond:
> Well, the first question anyone is going to ask is why
> on earth you are using 6.7.11?

Don't forget to use "OMG/LOL/derisno/perv" as in for example: "OMG, 
why are you using 6.7, are you a total perv? Derisno past! LOL." :)


There is a history to every product, and not only do we learn a lot by 
comparing past to present, but the latest version of LC that people 
take for granted owes a lot of fixes and some features to Paul in 
particular due to his meticulous work and testing, providing a huge 
benefit to the entire community!


It's wonderful to keep up with recent LC releases, especially where 
Apple is concerned, but sometimes circumstances and LC bugs/features 
can affect the speed of that process. Then you have people who grab 
the latest DP, precisely because it is the very latest thing, and get 
confused trying to tell the difference between their own bugs and DP 
bugs. I help people with that often enough to know that a chorus of 
"just grab the latest" is advice that needs clarification.


Paul:
> We are seeing a weird menu rendering issues under OSX

I believe this menu issue is also a current bug in LC 8.1.2! Haven't 
tried it yet in LC 9, but I will soon. LC 6.6 was okay, so it must 
have been introduced in 6.7 and remained until now.


Craig:
> I am hunkered down in v6 until I can swallow the new "look"
> of v8/9. The only thing I really miss from those is the new
> multi-char itemDelimiter.

Change for the sake of change keeps some people incredibly happy, 
others less so! The new interface does take some getting used to, and 
the old interface definitely had its strengths too, as I've realized 
lately with certain particular tasks and with teaching others. Much to 
learn from comparing and critiquing LC versions, enjoying the very 
latest as well as some past specimens!


Best wishes,

Curry Kenworthy

Custom Software Development
http://livecodeconsulting.com/


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your 
subscription preferences:

http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode