Re: Advantages of Memory based sqLite databases

2022-04-21 Thread Bob Sneidar via use-livecode
I made a client server proof of concept which encrypted messages before sending and decrypted them on the other end. The upshot was that I can send an encrypted query string from the client to the server, the server which handles the database connection stuff performs the query, then returns

Re: Advantages of Memory based sqLite databases

2022-04-21 Thread doc hawk via use-livecode
The difference between :memory: and the local hard disk is, in itself, stunning. I initially set up with mysql, and (iirc) disk sqlite. Whether it’s mysql or livecode’s fault, it isn’t (wans’t?) possible to to do a compound transaction to a mysql server. So when I opened a “file” (a couple of

Advantages of Memory based sqLite databases

2022-04-21 Thread Bob Sneidar via use-livecode
Hi all. Just an exercise in semi-futility here. I was curious about the actual difference in performance between querying a memory based sqLite database, as opposed to querying a mySQL database over a slow (iPhone hotspot) connection. I expected it to be significant, but HOW significant I had

:memory: heads up

2022-04-21 Thread Bob Sneidar via use-livecode
Hi all. I just wanted to alert anyone working with memory databases. Normally when you call revOpenDatabase("sqLite", filename) it will open the sqLite database with all the tables and data intact. HOWEVER... If you do this with ":memory:" instead of a filename then EACH TIME you call

Re: optionKeyDown message broken

2022-04-21 Thread Paul Dupuis via use-livecode
On 4/21/2022 3:27 PM, J. Landman Gay via use-livecode wrote: On 4/21/22 10:55 AM, Paul Dupuis via use-livecode wrote: In a new stack, place the following in the card script: on optionKeyDown pKeyName    if platform() = "MacOS" then put numToChar(charToNum(pKeyName)-128) into tKey1 --

Re: optionKeyDown message broken

2022-04-21 Thread J. Landman Gay via use-livecode
On 4/21/22 10:55 AM, Paul Dupuis via use-livecode wrote: In a new stack, place the following in the card script: on optionKeyDown pKeyName   if platform() = "MacOS" then     put numToChar(charToNum(pKeyName)-128) into tKey1 -- original sample from Dictionary     put

Re: optionKeyDown message broken

2022-04-21 Thread Paul Dupuis via use-livecode
Yes, there are work-arounds. My post was about confirming the bug so I can report it to Livecode. In this case, we have a shipping application in which the optionKeyDown handler USED to work that now a customer has (correctly) reported it broken. If everyone just codes work-arounds and bugs

Re: optionKeyDown message broken

2022-04-21 Thread Craig Newman via use-livecode
Have not played with your handler, but why not just: on rawKeyDown tKey if the optionkey is down then answer numToChar(tkey) end rawKeyDown Craig > On Apr 21, 2022, at 11:55 AM, Paul Dupuis via use-livecode > wrote: > > on optionKeyDown pKeyName > if platform() = "MacOS" then > put

optionKeyDown message broken

2022-04-21 Thread Paul Dupuis via use-livecode
I am finding problems with the optionKeyDown handler on both Windows (where it's the ALT key) and macOS (OPTION key). This is in Livecode 9.6.7 STABLE under macOS Mojave and Windows 10 In a new stack, place the following in the card script: on optionKeyDown pKeyName   if platform() = "MacOS"

Re: Encountering slow navigation to a card containing very large fields? Do this one simple trick

2022-04-21 Thread Bob Sneidar via use-livecode
Let me know off list if you want to have a look at the handlers I have written for getting data from a datagrid array into a memory database and back again so your queries can be more efficient. Bob S > On Apr 21, 2022, at 04:50 , David V Glasgow via use-livecode > wrote: > > > Thanks to