Pop up in a file?

I asked this one about a year and a half ago, but maybe someone knows
something new?

In the old days of 2D we would have a standard disclaimer on our
drawing sheet saying words to the effect of "may not be reproduced
without permission..." etc. You know the kind of thing I'm talking
about. In these days of electronic files tranferred via FTP, how can
we connect that kind of verbal information with a ProE part or
assembly file? We don't often issue 2D drawings with our files. So far
we have tried a cosmetic feature that is included in the start part
which we use to create all our part files. That gets a bit cumbersome
when you have an assembly up of 20 or so parts and they all have the
same disclaimer cosmetic in pointing in different directions. They're
all on layers of the same name so it's not too hard to blank them, but
we want them to be visible to the client when they first open the
file.


This is what I would like. When you open some programs (esp when
installing something) you get a little window that pops up which says
something you have to agree to terms and conditions and then you click
"yes" or "I agree" then move on to run the program or installation or
whatever. I would to be able to do that with a ProE file. You open it
and you have to read the disclaimer and tick it off before you can
open the file.


Has anything like this been suggested to PTC before? Could it be done
with Pro Toolkit or could something like a batch file be written into
the file? It seems like an idea whose time has come. I would have
thought it would be useful to a lot of companies.


Anyone got any suggestions? Somebody replied to my original post
saying that PTC's website has downloadable files that behave this way,
in order to enforce who owns the files. Maybe I should go to them?
They've always been so helpful.

 

This doesn't help me much, Dave. My clients DO have pots of money for
fighting Intellectual Property challenges. We patent a lot of the
stuff we do, usually design patents, but sometimes mechanical. It's a
very competetive business we're in. That's the way it is, and we're
thinking about how we can achieve this in our 3D files.

 

This doesn't help me much, Dave. My clients DO have pots of money for
fighting Intellectual Property challenges. We patent a lot of the
stuff we do, usually design patents, but sometimes mechanical. It's a
very competetive business we're in. That's the way it is, and we're
thinking about how we can achieve this in our 3D files.

In Western civilization, if you published it, including to the Internet, it's copyrighted. Period. Again, everyone knows this, then the lawyers get involved because some vigilant people have notified them that there are violators. And the lawyers slap them.

On the other hand, declarations of proprietary bolts, proprietary machined mounting brackets, proprietary stamped slides, proprietary anything-on-a-print does nothing to enforce the case. About the only thing proprietary statements do is say 'You may not copy this print and use it, in tact because we have our name on it.' It's a warning to the totally stupid and illiterate. Most such statements do their job because of the implied threat of legal action and the implied might of the legator. What the "Proprietary" statement has behind it is not much, since most are infinitly trivialized by the attempt to declare as proprietary, the most mundane, commonplace, unpatentable stuff that no one on earth would want to imitate.

All I can suggest, for judicious use, is an annotation feature, like the flying 3D note, that, through a locked parameter in the model, states the obvious~that this is your part. The only thing that comes close to your popups is a requirement when a drawing is created, that certain parameters be filled in, but even this is easily outflanked. On the other hand, let's take your popup seriously; someone clicks through it and agrees to it. How do you even know? how does this help you? wouldn't it be better, from a legal and contractual standpoint, to have signed NDAs on file before you deal with these people and send them anything? Signed non-disclosure agreements are actually legally binding. I doubt if your pop up boxes are because they leave no record. I'd ask some lawyers before bothering with this further.

David Janes[/QUOTE]

AFAIK we have NDAs with our vendors. But it's not really my problem.
This is what my company wants, and I was asking how we could achieve
it.

 

Bump.

I asked this one about a year and a half ago, but maybe someone knows
something new?

In the old days of 2D we would have a standard disclaimer on our
drawing sheet saying words to the effect of "may not be reproduced
without permission..." etc. You know the kind of thing I'm talking
about. In these days of electronic files tranferred via FTP, how can
we connect that kind of verbal information with a ProE part or
assembly file? We don't often issue 2D drawings with our files. So far
we have tried a cosmetic feature that is included in the start part
which we use to create all our part files. That gets a bit cumbersome
when you have an assembly up of 20 or so parts and they all have the
same disclaimer cosmetic in pointing in different directions. They're
all on layers of the same name so it's not too hard to blank them, but
we want them to be visible to the client when they first open the
file.


This is what I would like. When you open some programs (esp when
installing something) you get a little window that pops up which says
something you have to agree to terms and conditions and then you click
"yes" or "I agree" then move on to run the program or installation or
whatever. I would to be able to do that with a ProE file. You open it
and you have to read the disclaimer and tick it off before you can
open the file.


Has anything like this been suggested to PTC before? Could it be done
with Pro Toolkit or could something like a batch file be written into
the file? It seems like an idea whose time has come. I would have
thought it would be useful to a lot of companies.


Anyone got any suggestions? Somebody replied to my original post
saying that PTC's website has downloadable files that behave this way,
in order to enforce who owns the files. Maybe I should go to them?
They've always been so helpful.