Page 3 of 3

Re: Using a nicer Button "Pressed" state (than the default square)

Posted: Sat Mar 24, 2018 3:08 pm
by bogs
Richard, I know this isn't really a great way to spend your time, but I would seriously URGE you to make a throw away vm (8-10 gigs is MORE than sufficient), and put any of the *step systems on it.

Gorm works with objective C as its base, and if it isn't what xcode later became, I'd be shocked. As you noticed, the ui indeed looks like Mc/Lc, the undercode works just like xcode, has data binding and just about anything else you can imagine. Incredibly ahead for its time. The only thing really lacking is multi OS output standalones, but I can't be sure that isn't possible either.

@Richmond - Thank you for that link, you just *know* I am going to try it :D

To anyone else who ever finds interest in this, a lot of the *Step implementations after NeXT and OpenStep really do justice to the original vision. Using them really is as incredible as Mr. Jobs video linked by Richard.

Re: Using a nicer Button "Pressed" state (than the default square)

Posted: Sat Mar 24, 2018 4:02 pm
by richmond62
Here's a marginally better standard for that video:

https://allaboutstevejobs.com/videos/mi ... _demo_1992

Re: Using a nicer Button "Pressed" state (than the default square)

Posted: Sat Mar 24, 2018 10:25 pm
by bogs
Starting a new thread for NeXT and OpenStep :P

Sorry for hijacking your poor thread, teriibi, you are now returned to your regularly scheduled nice buttons :mrgreen:

Re: Using a nicer Button "Pressed" state (than the default square)

Posted: Sat Mar 24, 2018 11:20 pm
by jacque
teriibi wrote:
Wed Mar 21, 2018 9:45 pm
oK, one more try... :lol:
Is there anyway I can get rid of the "not suited" Square rectangle that appear when button is being pressed down and also after it has been released
I agree with Richard that shadows are out of vogue now and flat interfaces are the norm now. But if you still want to use a shadow, I'd just use the icon trick if you can't adjust the dropshadow settings to make it work. You could try changing the angle of the shadow to see if that helps. Otherwise, import two snapshots in the IDE where the shadow looks right, then assign those two image IDs to the icon and hilitedIcon in the button's property inspector.

SOLVED : Using a nicer Button "Pressed" state (than the default square)

Posted: Sun Mar 25, 2018 3:09 am
by teriibi
@fourthworld !
turn off the showFocusBorder property and let us know if that goes away.
YEAHhhhh...that was it, solved the "unwanted effect" !
( so its not a bug at all Woooopss :lol: )
Thanks. :wink:

Re: Using a nicer Button "Pressed" state (than the default square)

Posted: Mon Mar 26, 2018 8:51 am
by richmond62
At the risk of being slightly tangential here's a picture of a standard LiveCode button with a standard drop shadow in RC/LC 4.0 (on the left) and LC 8.1.9 (on the right).
buttons.png
What I find interesting is how the angle of the drop shadow as well as the fontSize
has been changed (without any consultation as to whether users want that change).

Re: Using a nicer Button "Pressed" state (than the default square)

Posted: Mon Mar 26, 2018 4:57 pm
by FourthWorld
Default fonts, and baselines on which they're rendered, have been significantly improved by popular demand in recent versions to better match OS HIGs.