How to keep your variables in the design?

Since these attachments are viewed as data blobs by the Allegro database; I do not see why Cadence would delete them in future releases.

Since the attachments are visible to any Skill program, if you do not want your users to access the raw attachment, you can add a password when creating the attachment. Then accessing or deleting the attachment would require a password which only your application code would know. For real paranoids, you could then encyprt your skill file so nobody could reverse engineer the password.

Hi

Use of a password for the attachment does not make sense unless the skill program is encrypted

Having the skill program encrypted, what use is the attachment for a user?

I can see two QuickView attachments in a 16.5 board, but what can I use that information for? fxffxf would you recommend use of a password for attachments?

Best regards

Ole

The basic issue with application attachments without password protection is that they rely on the good behavior of other Skill programmers. No password protection assumes that no other Skill programmer will muck with your attachment since they didn't create it.If you are  developing and using Skill programs within one company this may be a good assumption.

For example, you can write some Skill code to replace the TIF Quickview attachment with some other data and see what happens when Allegro attempts to use this attachment. If Quickview application code password protected this attachment then it knows the data is valid since only it can modify the attachment.

You must remember that attachments are a storage mechanism for user data. A Skill program is usually interacting with the user through some UI like a form to present this stored data. Storing the attachment password protected and encyrpting skill is code doesn't prevent this use model it just adds a level of security.

 No, my paranoia is not concerned with the protection program or attachment. I scared that my attachment can break the project into future releases.
Thanks guys, you reassured me.
But the password for the attachment - it's good tip, it will protect the attachment from accidentally (or not accidentally) overwriting. I'll have it in mind for the future.

Hi

Taking this discussion one level further.

I have an attachement with several settings in a board and retrieve it.

How can I easily change just one attachment setting using axlSetAttachment without having to traverse all settings.

e.g.,

a_id = axlGetAttachment("ns_prog_settings" 'string)

mylist = car(errsetstring(a_id->data))

mylist has several settings like

mylist->width

mylist->spacing

my_list->startx

my_list->starty

but I would just like to change mylist->width and save that back to the attachment.

axlSetAttachment takes an open attachment as the argument, so that is a_id in this case, but I cannot find an easy way to manipulate a_id without having to traverse all settings and a_id->width does not seem to bring me anything usefull except all the values.

axlSetAttachment(a_id) does give a new attachment but no changes.

How can this be accomplished?

Best regards

Ole