> I am trying out a Matrox Pahelia graphics card on a Inventor 6 and XP Pro.
> The first problem that I am encountering is that when I go to any
Parameters
> window and double click on an Equation variable field it doesn't respond.
> Has anybody seen this type of behavior on any other cards?
>
Here's where things stand on the above Matrox Parhelia problem:
I contacted Matrox through their online forum and described my problem along
with model and serial number of graphics card, OS, hardware setup, IRQs,
etc.
The Matrox guy obtained a copy of Inventor and loaded it to trouble shoot
the problem. As he wasn't an Inventor user here is what I told him to do:
_______________________________________
-Work your way through the introductory setup stuff and welcome screens so
that you get access to the menu bar on top and select File>New and then it
will go to a window with templates.
-Select any template with an .ipt extention and hit Okay.
-You will then see a screen with tools on the left side. Select the
rectangle tool. Move the cursor to the drawing window and left click
somewhere to select a start point and left click again in a different place
to finish the rectangle. Right click and select Done.
- Click on the Parameter tool which looks like a mathmatical Function
symbol. That will bring up a Parameters window.
- In the parameters window select Add. Type in any sort of parameter name. I
forgot if there are any syntax rules for a parameter so keep it simple. Hit
enter. The blue row created should have a default value created in the
Equation column and in the other columns.
On my Parhelia system I can not click on that field. It does not open for
data entry.
_____________________
So he ran the instructions and responded back to me that he wasn't seeing
the problem. He was able to enter data in the Equation column.
I then went back to my Matrox machine and tried it again and found that this
time I could enter the data in the field.
I was about to send a message to the Matrox forum telling him this but first
checked the forum and found that he tried it out on another machine and was
experiencing the problem. And then he came back to his first machine and
was also seeing the problem.
He then reloaded Inventor and the problem was gone.
He thinks it is an Inventor problem. Since I haven't seen this problem
reported on this newsgroup I think it must be the card but at this point I
don't know. What do you guys think?
Steve Krause
sk@dolby.com