In article <32qmjh$5rq@rzsun02.rrz.uni-hamburg.de>,
James Anderson <anderson@kogs11.informatik.uni-hamburg.de> wrote:
>I want to implement a user interface to an areal image interpretation system
>(-: which I will implement in the next two weeks :-). I would like to use
>Hipworks (Beta), but after much reading of HELP, TEACH, and REF files, and hearing
>those bl**dy fireworks too often, I still have two questions. I know that I have
>read the answer to one of them some time today, but I can't remember the answer and
>I can't remeber where I read it.
>
>Q1) How can I read the script of the Walker demo?
> (I want to import a 10 MB image.)
Well, the answer to Q1 is in HELP * HIP_NEWS :-) Do:
true -> hip_system("currentStoryboard")("canAuthor");
"normal" -> hip_system("currentStoryboard")("menuBar");
>Q2) How do I use propsheets within Hipworks?
> (I want to specify parametric ranges so that, for example, I don't have to
> import the whole of a 10 MB image.)
Well, you can look at how it's done in the Tours production... In the
HiPWorks V1.2 there is a "hipPropBox" storyboard property which enables you to
treat the current storyboard window as a Propsheet propbox. I'm afraid I can't
remember if the Beta version had an equivalent --- it may well be done by some
horrible hack in that version.
>P.S. The really worrying thing is you get one of these 10 MB images every time you go
> "click" - and one of the cameras goes "click" every second.
<he he> good luck!
Adrian
aids (adrianh@cogs.susx.ac.uk) ObDisclamer: Poplog used to pay my wages
Phone: +44 (0)273 678367 URL: http://www.cogs.susx.ac.uk/users/adrianh/
|