Default button - Issue or not

LiveCode is the premier environment for creating multi-platform solutions for all major operating systems - Windows, Mac OS X, Linux, the Web, Server environments and Mobile platforms. Brand new to LiveCode? Welcome!

Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller

Post Reply
terryw64
Posts: 8
Joined: Tue Feb 17, 2015 1:06 am

Default button - Issue or not

Post by terryw64 » Fri Feb 20, 2015 9:53 pm

Thanks to all who have assisted me in my previous post I have another issue or not.

Livecode community 7.01 on a MAC. Running Yosemite 10.10.

I have a mainstack with the default card, then a default button and several other various controls (Radio, Checkbox, Tabs, etc..) on it. I've attached no code. If I click any other controls on the mainstack, the default button will turn white until the mouse button is released. So, then I go to the button properties, uncheck the 'Default Button' option, the set it to back to check. This resolves the issue. A known bug?

dunbarx
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 10305
Joined: Wed May 06, 2009 2:28 pm

Re: Default button - Issue or not

Post by dunbarx » Fri Feb 20, 2015 11:20 pm

Hi.

There is a property change when you unset and reset that property. The "armed" property is changed from "true" to "false". Does it seem counterintuitive, that the process is not transparent, that is, the state before is different than the state after, even though it seems that nothing should have changed?

Whether this can be exploited, or should be, is a question Is it more like a feature than a bug?

Craig Newman

Post Reply