protecting dynamic blocks

[samifox]

Hi

i want to develop commercial dynamic blocks, 

is there a way to protect them against piracy?

 

Thanks

S

[rkmcswain]

On the technical side? No.

 

On the legal side? Perhaps a contract that forbids the sharing of drawings that contain said blocks with others? But that pretty much restricts the ability for an entity to share drawings, within the terms of that contract. So it would either get violated, or your customer would just not agree to it.

[samifox]

it should be a thought, 

we spend lots of time and afford designing dynamic blocks while others can enjoy them for free.

why Autodesk can't do those blocks dynamic only if the author allows it?

[maratovich]

40 minutes ago, samifox said:

it should be a thought, 

we spend lots of time and afford designing dynamic blocks while others can enjoy them for free.

why Autodesk can't do those blocks dynamic only if the author allows it?

 

File protection - only viewing and printing, it is possible when using special protection.
Block protection ..... block inside the file .... this is a standard drawing object ... it's just so impossible.
It is necessary to create new primitives, from other users they will be a proxy. You will need to use Enambler, you can sell it ....
It's all theoretically ...
The idea is paid

Edited September 14, 2018 by maratovich

[samifox]

Everything is possible. In etransmit dialog add a check mark "disable dynamic blocks" . So the end user will get the same blocks but static. 

[maratovich]

15 minutes ago, samifox said:

Everything is possible. In etransmit dialog add a check mark "disable dynamic blocks" . So the end user will get the same blocks but static. 

In my entire life, I have not seen a man who used etransmit.
Met a couple of times on the forum.
Usually send one separate file.
Consider this.

[samifox]

It's impossible not to use etransmit in this age where we use so many references.

[Aftertouch]

I prefer to create 'BINDED' files instead of E-Transmit..

Most customers just dont understand E-Transmits....

[dlanorh]

The only sure fire way to protect dynamic blocks is to exploded them, which kind of defeats the reason for dynamic block. If you sell them, there is no way of controlling what the client does with them.

[hanhphuc]

On 9/19/2018 at 8:39 PM, dlanorh said:

The only sure fire way to protect dynamic blocks is to exploded them, which kind of defeats the reason for dynamic block. If you sell them, there is no way of controlling what the client does with them.

 

$0.02 another suggestion without exploding

1. without coding - SaveAs lower version < 2006 or dxf

2. with code - activeX method - renaming or anonymous

(vla-converttostaticblock blk "bname")

(vla-converttoanonymousblock blk)

then purge

[RobDraw]

You simply cannot prevent piracy. 

[BMRVisuals]

Had this issue until recently, I've since come across a Lisp routine that removes all dynamic properties before issue.

 

Still maintains all the blocks as blocks; and retains visibility properties, but removes all controls.

 

We've now made this a standard practice before issuing DWG files to protect our content. 

[nod684]

On 9/13/2022 at 9:04 PM, BMRVisuals said:

Had this issue until recently, I've since come across a Lisp routine that removes all dynamic properties before issue.

 

Still maintains all the blocks as blocks; and retains visibility properties, but removes all controls.

 

We've now made this a standard practice before issuing DWG files to protect our content. 

 

Can you share the lisp?

[Steven P]

Though a half competent draughtsperson could remake them dynamically