Datagrid behaviour script

Got a LiveCode personal license? Are you a beginner, hobbyist or educator that's new to LiveCode? This forum is the place to go for help getting started. Welcome!

Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller

Post Reply
kevin11
Posts: 101
Joined: Thu Aug 11, 2011 5:02 pm

Datagrid behaviour script

Post by kevin11 » Fri Aug 19, 2011 9:49 am

Hi,

I'm happy so far with my datagrids - they seem to be doing the job.
However, when setting up a datagrid, and clicking on the Row behaviour button, I always get a script called button "behaviour script", regardless of the name of my datagrid. This is fine, until I want to edit multiple datagrids, all of which seem to be controlled by different scripts but with the same name.

Any way I can name the script that governs row behaviour to something different ? Can't find it in docs....

Thanks !

nlexa
Posts: 26
Joined: Fri Aug 05, 2011 2:34 am

Re: Datagrid behaviour script

Post by nlexa » Wed Nov 30, 2011 5:05 am

Any way I can name the script that governs row behaviour to something different ?
When you have a lot of those behaviour scripts up and they are all named the same thing, "Behavior Script" it does get confusing.

All you have to do is change the name of the button the script is on from "Behaviour Script" to "EnterANameHere".

The group that uses the script button references the button by id so as long as you dont change the id, I figure it will work. (I have tried this quickly just now to be sure)

You could also comment in the top of the script

Code: Select all

##EnterANameHere
to help you identify which behaviour script you are working on.

To change the name of the button the script is on you need to find it using the Application Browser in the Tools drop down menu. It will be in the DataGrids substack on one of the cards. Follow your nose.

Hope this helps 4 months late.

kevin11
Posts: 101
Joined: Thu Aug 11, 2011 5:02 pm

Re: Datagrid behaviour script

Post by kevin11 » Wed Nov 30, 2011 3:10 pm

Thanks for the response.

However, we are now considering leaving LC as a development platform. We are currently looking into other solutions for app development.

Post Reply