ImagePro>Bugs or Features?


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

ImagePro>Bugs or Features?




I have found a few annoyances when moving things from IPbasic to VB.

FOr example, the IpSegSetRange(0,0,0) call will generate a divide by 0 error
in
VB, but seems to run ok in IPbasic.  I assume that IPbasic just ignores the
divide by 0
and is set for "On Error resume next" by default.
If I have VB ignore the divide by zero with "On Error resume next", then IP
does the correct thing and
sets the range to select all pixels with a value of 0.  I assume it is the
range of 0 to 0 that generates a divide by 0 even though this is the only
valid way to specify that you only want the pixel 0.  A pixel range of 0
should not generate a divide by zero.  Are any bad things happening
internally with this divide by zero or is it safe to ignore.

Several constants seem to be missing in the ipc32.bas that gets generated
with the VB SDK wizard.
In particular things like
GETCHANNEL
GETRANGESTATS
These constants are in the regular ipc32.bas that is in the image pro
directory.
If I copy over the GETRANGESTATS into the SDK ipc32.bas then it seems to
work fine.
I hesitate to just copy things from one version of ipc32.bas to another
since there
are countless differences between these two files.

The rotate command seems to have a bug when dealing with sequences.
If you call it from the menu (with apply to sequence selected instead of
just frame)
then it will produce a rotated sequence.  If you call it from code (macro or
VBbasic)
it will not rotate the sequence, but only the frame.  It doesn't seem to
help if you select the
apply to sequence icon on the screen or set it in the code first with
IpseqSet(SEQ_Apply, 1).

I think there was also an old bug from way back on blb counts of 0 that I
haven't checked recently.
Basically the stats array from IpBlbGet(GETRANGESTATS) does not get cleared
if you have a 0 blb count.
You will get a 0  count from GETNUMOBJ, but the number of objects and stats
reported in the stats array
will correspond to the last non-zero count measurement.  Basically you can't
trust the stats array unless
you check the GETNUMOBJ count.  If the  GETNUMOBJ count is zero then the
stats array (including count) is out of date.


Just thought I would report these in case anyone else ran into them.

Mike Plonski


BEGIN:VCARD
VERSION:2.1
N:Plonski;Michael
FN:Michael Plonski
ORG:Plonski Engineering
TITLE:President
TEL;WORK;VOICE:(310) 373-0318
TEL;WORK;FAX:(443) 269-0753
ADR;WORK:;;9 Roanwood Drive;Rolling Hills Estates;CA;90274;United States of America
LABEL;WORK;ENCODING=QUOTED-PRINTABLE:9 Roanwood Drive=0D=0ARolling Hills Estates, CA 90274=0D=0AUnited States of =
America
EMAIL;PREF;INTERNET:mplonski@cox.net
REV:20020917T215814Z
END:VCARD
***********************************************************
This message was sent to you because you are subscribed to <imagepro-users@lists.mediacy.com>.
TO UNSUBSCRIBE, send an email to: <imagepro-users-off@lists.mediacy.com> 
To switch to the DIGEST mode, email to <imagepro-users-digest@lists.mediacy.com>
To switch to the INDEX mode, email to <imagepro-users-index@lists.mediacy.com>
Send administrative queries to  <imagepro-users-request@lists.mediacy.com>
To SUBSCRIBE or UNSUBSCRIBE visit http://www.mediacy.com/tech/subscriber.htm
***********************************************************
Need an Image-Pro macro or driver? Find it at http://www.Solutions-Zone.com
Got an Image-Pro macro or driver? Add it to http://www.Solutions-Zone.com
***********************************************************




Search this Archive