J. Landman Gay wrote:
> On 1/17/17 2:27 PM, Richard Gaskin via use-livecode wrote:
>> I was curious about performance, so I ran the test copied below, with
>> these results:
>>
>> MenuItem: 219 ms
>> As text: 10 ms
>
> Do the results change if you lock menus before changing them?
> Manipulat
On 1/17/17 2:27 PM, Richard Gaskin via use-livecode wrote:
I was curious about performance, so I ran the test copied below, with
these results:
MenuItem: 219 ms
As text: 10 ms
Do the results change if you lock menus before changing them?
Manipulating menus, especially on Macs, is expensi
At 12:49 PM -0500 1/17/2017, Paul Dupuis via use-livecode wrote:
For desktop applications on Windows and OSX, I am lookingf or what
people consider the best practice to be for enabling, disabling, or
updating menu items based on context.
You have so many ways in the LiveCode language to do this:
Richard,
Thanks for the timing information. It was reassuring to see changing the
text was faster. In dealing with bug
http://quality.livecode.com/show_bug.cgi?id=19097 I have been looking to
clean up menu code and was looking for best practice feedback exactly
like yours. My own inclination has b
Paul Dupuis wrote:
> For desktop applications on Windows and OSX, I am lookingf or what
> people consider the best practice to be for enabling, disabling, or
> updating menu items based on context.
>
> You have so many ways in the LiveCode language to do this:
>
> enable menuItem 2 of menu "Edit"
For desktop applications on Windows and OSX, I am lookingf or what
people consider the best practice to be for enabling, disabling, or
updating menu items based on context.
You have so many ways in the LiveCode language to do this:
enable menuItem 2 of menu "Edit"
disable menuItem 3 or menu "File
