UltraCard Appologies
15 messages in this thread
To All UltraCard Owners and other CIS users:
Appologies for the long delays in responding to mail and update requests.
During September there was a death in my family and my 3yr old daughter had an
emergency hospital stay. The combination of these two made September a month
in which we were unable to respond to much in anything resembling a timely
fashion.
All these problems have now been resolved, we have moved our offices into
better quarters and we are "back in the saddle" and proceeding ahead full bore.
UltraCard 1.3 is now complete (check the DL area) and registerd owners who have
sent in their disks for update and have not yet received them will be receiving
the 1.3 version. Other owners may download the 1.3 version from our BBS (the
number's in your manual). Or you may, once again, send in your disk for a
free update. Our turnaround on updates is now next-day after receipt. We have
added staff to handle the market's response to UltraCard and thank you for your
continued support and patience.
Sincerely, Mike Lehman, President, Intuitive Technologies.
Mike:
I left some E-Mail on your board. Have you had a chance to catch up?
Anyway, I have UC 1.2.1, and, if I compact my projects regularly, and create
them from a vd0:, I don't have too many problems.
Also, I dl'd your 1.3 UC Browser and the Samples1 stack. The grpahics are
wonderful, but, for some reason, only one of the sound files plays (the one
where first the Amiga voice speaks, and then the woman's voice says something
like "or you can use digitzed sound").
I keep getting these requestors that say "not enought memory to load sound"
when I read that stack (and then of course "can't find sound to unload" later).
I have 3 megs of 16 bit ram, and 2 or 32 bit ram. I don't, however, yet have
obese agnus. Does this stack require it (I noticed it really eats chip ram, at
least on my system).
Ray Lewis
Ray, you MUST have all the sound files in ULTRA:STACKS IF you don't then you
will get the "not enough memory to load sound" msg. If that's not the problem
please let me know. Mike
That was the problem, Mike. If you specified that in the instructions on the
BBS, I missed it. I unpacked it into a "stacks" dir in vd0:, and ran it from
there. When I read you instructions here, I un-assigned Ultra: from my
dh0:UltraCard dir, and reassigned it to vd0:. Worked like a charm.
(Nice job, too).
Since I have your ear (eye, whatever), maybe you can help me with a stack I'm
working on. I have 12 buttons, the twelve tones of the European scale. I'm
"highlighting" them by putting a similar button, but with different colors, on
top, and making it invisible. When you click on the visible button, it "set
visible [invisible button] true", and when you click on that one, it does the
opposite. Works great.
However, since only ONE of these buttons should be "lit" at any time, when you
click on the unhighlighted button, it should also turn off whatever is on.
Right now, the only way I can get this to work is to have it first turn off ALL
TWELVE, and then turn on the right one. This is slow. I'd rather save the
name of the currently "on" button to a variable, and then have the program
first "set visible [variable] false", and then turn itself on, passing its own
name to the variable, so it will be turned off in turn when the next button is
clicked.
I'm sure there is a way to put the name of a gadget into a variable, and then
have that variable dump it out into a command line, but I can't for the
<continued>
<continuation>
life of me figure it out. I've created and initialized a GLOBAL variable in
the backdrop, the frame, AND the stack. But, when I use that variable's name
in the "set visible BUTTONKILL false", the program says it can't find
"BUTTONKILL".
HELP>
Ray Lewis
Ray, you need to use the OBJECT() function. You pass it the id of the object
in question (such as OBJECT(15)) and it will indirectly reference it. When a
button is clicked and sets itself on the global variable "ME" is set to the id
of the button clicked so you could: PUT ME INTO RECENT.HILITE (providing you
declared RECENT.HILITE as a global) and then use it to turn off that when you
need to. as in SET VISIBLE OBJECT(RECENT.HILITE) FALSE. Mike
Thanks Mike. I'll play around with that.
(Please get the expanded docs on your board soon, so I won't have to ask basics
like this.)
So far, I'm having a ball with UC.
Ray Lewis
Just finished new, glorious, 150+ page UC manual. Includes MANY MANY
enhancements including a complete language reference and a operating reference.
This will be available for download in next week or so, as well as in printed
form. Mike
Mike:
I can't wait! Thanks. I'll keep an eye out for it.
Ray Lewis
Mike, I thought that a manual was the most important thing missing!
Great!
— Ethan
Remember, Mike, if you want to send it to me on a disk, I will proofread it for
you. (I just sent in my original UC disk for update, so you'll be mailing to
me fairly soon anyway.)
Regards,
Jim
Ventola
Jim, thanks for your support. I'll let you know. Mike
Ray,
The reason you get that distorted voice on that screen is because of the
bus contention between the medium res screen and the narrator device.
Steve
Steve,
I didn't get distortion. The sound files didn't load. Turns out, I hadn't
"assigned" ULTRA: to the dir in which I had the stack.
Ray Lewis
Oh, I see. I did get distortion on one of the screens, and I thought that's
what you were talking about.
Steve