Anyone got an xTalk algorithm for converting between standard and Julian
dates they can share?
Richard, check out the following functions from the stack script of my
jonesLib stack:
function dayNum
function julianDate
function gregorianDate
The functions dayNum and julianDate offer different
Richard,
Anyone got an xTalk algorithm for converting between standard and Julian
dates they can share?
--Georgian to Julian Date converter
put the short date into now
convert now to dateitems
put item 1 of now into year
put item 2 of now into month
put item 3 of now into day
Yes, the real problem is that the mac lib wants to crash whenever I give it a
GWorld instead of an ordinary window. Maybe I'm missing something...
Anyhow, I actually got a pointer to the window in a more round-about way: I
used the pixMapID of the stack and looped through the window list,
Man, gotta love the community on this list. Thanks to the folks who sent
the Julian snippets -- saved me some time, and I very much appreciate it.
This raises a question: Wouldn't it be cool if there were some repository
of such snippets, like a code stream we could dip into when we're thirsty
SuperCard provides the at loc option to the ask and answer commands for
more control over where it appears.
I see the syntax isn't there, but is there a property to do this in MC? Or
would it be best to write custom dialogs in such cases?
--
Richard Gaskin
Fourth World Media Corporation
Richard,
Anyone got an xTalk algorithm for converting between standard and Julian
dates they can share?
--Georgian to Julian Date converter
put the short date into now
convert now to dateitems
put item 1 of now into year
put item 2 of now into month
put item 3 of now into day
Yeah, it's called mctools.org. Unfortunately it's dry as a
bone, seems the list is very helpful in answering questions but
not actually submitting links, source, stacks or tips. Having
worked for a client where I was bound by confidentiality I can
understand some people not having the right
What is the magic of properties which will let me leave the traversalOn on
for a field (so that it can be typed into), yet when the window gets focus
the field will not automatically also get focus?
Am I to resort to having an offscreen dummy field to avoid unwanted opening
of the visible field?
[EMAIL PROTECTED] wrote:
Yeah, it's called mctools.org. Unfortunately it's dry as a
bone, seems the list is very helpful in answering questions but
not actually submitting links, source, stacks or tips. Having
worked for a client where I was bound by confidentiality I can
understand some
Well, you could create a button with all properties except traversalOn
turned off, and make it layer #1. That way, when the window opens, the focus
is on the button, but there is no visible indicator that it has the focus.
Tab once, and you go to the field.
I'll look for a cleaner way...
Ken
Here's two more:
#1)
on openCard
click at 1,1 -- assuming you don't have something there
end openCard
OR
#2)
on openCard
set the traversalOn of fld 1 to true
end openCard
on closeCard
set the traversalOn of fld 1 to false
end closeCard
This will have the effect of having the field's
John,
Thanks for your comments.
Besides, arrays *are* multidimensional. For example:
put 1 into a[1,3,7] # three-dimensional array
put a[a[1,3,7],a[1,3,7]+2,a[1,3,7]+6] returns 1
Yes I'm aware of this - and it is a useful feature for certain things like graphics.
Really though this is
12 matches
Mail list logo
