I like the way the new tab buttons work - setting the uTabId and uTabText properties in the parent object, so I was thinking of making the existing option buttons work in the same way. Can anyone think of any downsides? V0.13 - bugfix
Moderators: heatherlaine, kevinmiller, robinmiller, malte, splash21
-
splash21
- VIP Livecode Opensource Backer
- Posts: 369
- Joined: Sun Dec 19, 2010 1:10 am
- Location: UK
- Contact:
V0.13 - bugfix
V0.12 had a bug in the new tab buttons that prevented you from changing their color after the card was renamed. Thanks to @doobox for spotting it early - the update is on-line!
I like the way the new tab buttons work - setting the uTabId and uTabText properties in the parent object, so I was thinking of making the existing option buttons work in the same way. Can anyone think of any downsides?
I like the way the new tab buttons work - setting the uTabId and uTabText properties in the parent object, so I was thinking of making the existing option buttons work in the same way. Can anyone think of any downsides? LiveCode Development & Training : http://splash21.com