Richmond...
from the dictionary... 'If the control is an unlocked field . the
openField message is sent to it instead of the focusIn message.'
Is your field unlocked ?...:-)
Date: Wed, 25 Mar 2015 08:57:47 +0200
From: richmondmathew...@gmail.com
To: use-livecode@lists.runrev.com
I tried this:
on focusIn
set the backGroundColor of fld CHAMP to green
end focusIn
and it didn't work.
I wanted to change a field's backGroundColor when someone selects that
field;
obviously THAT method doesn't work.
Richmond.
___
use-livecode
On 25/03/15 09:14, John Dixon wrote:
Richmond...
from the dictionary... 'If the control is an unlocked field . the
openField message is sent to it instead of the focusIn message.'
Is your field unlocked ?...:-)
Cannot see any difference really.
Date: Wed, 25 Mar 2015 08:57:47 +0200
Now that I think about this, is this a 'feature' of revExecuteSQL ? A
string that looks like a time gets coerced by the command into a time and
adjusted for time zone without regard to the field type of the destination
database field. Can that be what's happening?
On Tue, Mar 24, 2015 at 9:48
Hi Paul,
MySQL definitely doesn't guess that your string consists of two times
and definitely doesn't guess that it should be converted depending on
time zone.
MySQL doesn't interprete a string as a date if the field for that string
isn't defined as a date. Your field is defined as VARCHAR
LC 7.0.3
New stack, two new fields with their lockText set to true.
In both fields their scripts:
on focusIn
set the backgroundColor of me to green
end focusIn
on focusOut
set the backgroundColor of me to red
end focusOut
Pressing the Tab key moves the focus from one to the other and the
Thanks, Mark.
On Wed, Mar 25, 2015 at 1:27 AM, Mark Schonewille
m.schonewi...@economy-x-talk.com wrote:
Can you confirm that the MySQL syntax you see in the message box is the
same as what you entered in Sequel Pro?
In Sequel Pro, I wrapped the time period in double quotes.
When we tried
On Tue, Mar 24, 2015 at 7:26 PM, J. Landman Gay jac...@hyperactivesw.com
wrote:
I've never used behaviors in menus. The Edit menu is the easiest to
script, the engine keeps track of everything for you. You only need a
single word for each switch item to cover the basic stuff. Here's my
On Tue, Mar 24, 2015 at 5:24 PM, Terry Judd terry.j...@unimelb.edu.au
wrote:
Try one or more of focusedObject(), selectedField(), selectedChunk()
Naturally, when I went back, the menu *was *getting called.
One more intermittent thing to debug . . .
--
Dr. Richard E. Hawkins, Esq.
(702)
I got things a bit wrong as I wanted the field backGroundColor to change
when
end-users selected a field, so, after going for a walk I changed things
to the far simpler:
on mouseEnter
set the backGroundColor of me to green
end mouseEnter
on mouseLeave
set the backGroundColor of me to
On 24 Mar 2015, at 21:15, Richard Gaskin ambassa...@fourthworld.com wrote:
Thanks for filing the bug report. I've added the Mozilla link.
For information:
thank you for logging this report and getting back to us with a sample stack.
We have now confirmed the bug in your bug report and
As Mark said, it's hard to believe mySQL is doing this. The other element
is Sequel Pro - not likely but maybe it's doing the time conversion?
Have you tried selecting the data with Livecode (revDataFromQuery)?
On Wed, Mar 25, 2015, 7:18 AM Paul Foraker p...@whitefeather.com wrote:
Thanks,
Well, there is no difference except that different messages are sent under
different conditions.
That seems different to me.
Whether each message ought to be sent in both cases, or rather, why do we
need to distinguish at all, is perhaps a question. It might be useful, after
all. But it should
This of course ,limits Select All to text in fields. Combo Boxes are excluded
as they are buttons. Easy enough to account for though.
Bob S
On Mar 24, 2015, at 19:26 , J. Landman Gay
jac...@hyperactivesw.commailto:jac...@hyperactivesw.com wrote:
case select all
if the selectedfield
Not necessary in one shot INSERT/UPDATE/DELETE because SQL does it for you
behind the scenes if you don't issue the BEGIN/COMMIT your self.
However, if you have a logically related set of INSERT/UPDATE/DELETE
statements, even if it's only two, it's absolutely necessary for database
integrity
Just to be clear, using BEGIN and COMMIT is called transactional. It’s purpose
is to be able to ROLLBACK if any errors occurred. This not only includes SQL
errors (which should not be happening if you control the SQL and data), but
internal errors, like for instance you insert an invoice then
Whoops! Thanks for letting me know about the 404 error - will go to fix it
right now.
SQLIteAdmin does have query/sort features but, just to be clear, it is a
standalone program so you can't see the code.
Pete
On Tue, Mar 24, 2015 at 7:14 PM JB sund...@pacifier.com wrote:
Hi Peter,
Thank
The same Edit script should work as a behavior. (It does assume Select All is
for text, but I think that's what you're working with.)
On March 25, 2015 8:43:22 AM CDT, Dr. Hawkins doch...@gmail.com wrote:
On Tue, Mar 24, 2015 at 7:26 PM, J. Landman Gay
jac...@hyperactivesw.com
wrote:
I've
Sorry,
make that
---
modTableField 0_3_2
---
Kind regards
Bernd
--
View this message in context:
http://runtime-revolution.278305.n4.nabble.com/ANN-modified-Table-Field-0-2-2-tp4690621p4690622.html
Sent from the Revolution - User mailing list archive at Nabble.com.
Bernd:
Thanks!
Bill
On Mar 25, 2015, at 12:01 PM, BNig bernd.niggem...@uni-wh.de wrote:
Sorry,
make that
---
modTableField 0_3_2
---
Kind regards
Bernd
--
View this message in context:
Okay, thanks! I have been looking
a SQLYoga and see it has search,
sort and find.
It seems to use arrays but with using
large amounts of data in a data grid
you need to use a cursor.
SQLYoga does provide the ability to
use cursors but since it is using the
arrays is that using a lot of memory?
bug 15079 http://quality.runrev.com/show_bug.cgi?id=3D15079
http://quality.runrev.com/show_bug.cgi?id=3D15079
not a bug. Sorry for bad report. My problem with understanding how the =
password protection works.
Best,
Bill
On Mar 24, 2015, at 12:24 PM, bugzilla-dae...@meg.on-rev.com wrote:
Thanks for the reply and infer. Bob!
Your info always helps a lot.
John Balgenorth
On Mar 25, 2015, at 9:53 AM, Bob Sneidar bobsnei...@iotecdigital.com wrote:
Just to be clear, using BEGIN and COMMIT is called transactional. It’s
purpose is to be able to ROLLBACK if any errors occurred.
Dear list,
here is a new version of modTableField.
It is a way to display tabular data in a table view.
--
http://berndniggemann.on-rev.com/modTableField/modTableField_0_3_2.zip
--
modTableField_0_3_2 has been cleaned up and has more examples and
Thanks, Mike!
I have no doubt what I will be
using now. Good info thanks.
John Balgenorth
On Mar 25, 2015, at 1:16 PM, Mike Bonner bonnm...@gmail.com wrote:
Part of the slowdown when inserting a large number of rows one at a time is
the opening and closing of the transaction file. If you
My latest product, SQLMagic, is inching slowly to a GM release. Using it,
you will not need to write any Livecode scripts or issue an SQL statements
for a large percentage of your SQL transactions. Email me offline if you
would like to be on my SQLMagic mailing list.
On April 16th, I am
It would be nice to have a good stack
with all of the power and tricks using
SQL with Livecode.
I would even pay for it. Any power
users want to make a few dollars?
If you do I personally thinks it should
be code examples instead of some
hidden library etc.
John Balgenorth
On Mar 25, 2015, at
I am not surprised. A lot of developers do not know the power and tricks of
presenting and performing data via SQL language.
Mike Bonner bonnm...@gmail.com wrote:
Part of the slowdown when inserting a large number of rows one at a time is
the opening and closing of the transaction file. If
On Wed, Mar 25, 2015 at 8:08 AM, Peter Haworth p...@lcsql.com wrote:
Have you tried selecting the data with Livecode (revDataFromQuery)?
Well, thank you very much. When I checked with revDataFromQuery, I saw the
same problem we're seeing in Sequel Pro. That was a clue! Sure enough, our
Part of the slowdown when inserting a large number of rows one at a time is
the opening and closing of the transaction file. If you want to see this
in action, you can set a loop up to do repeated single row inserts, then
watch in your file browser next to the db file as the transaction file
Great, glad you figured it out.
On Wed, Mar 25, 2015 at 1:35 PM Paul Foraker paul.fora...@gmail.com wrote:
On Wed, Mar 25, 2015 at 8:08 AM, Peter Haworth p...@lcsql.com wrote:
Have you tried selecting the data with Livecode (revDataFromQuery)?
Well, thank you very much. When I checked
I saw the SQLMagic seminar at RR 13. It was very impressive. The beginner can
dive into databases immediately. Even experts can benifit as well as the
beginner. Experts can set up data entry screens with complex schemas in a flash.
Ralph DiMola
IT Director
Evergreen Information Services
Was rummaging through boxes of stuff looking for something when I came
across a few ADB keyboards and mice. Thought to myself, 'it's about time to
turf these, no one, not even Richmond, could possible want them'. Seems
like I could be wrong:
http://kernelmag.dailydot
33 matches
Mail list logo
