LiveCode Forums

It turns out that you can only set the monthNames if the "namesToUse" are set to "Custom" this works for me with widget DatePicker on mouseUp pButtonNumber set the namesToUse of widget 1 to "Custom" set the weekStartsOn of widget 1 to "Sunday" set the "MonthNames" of widget 1 to "JAN,FEB,MAR,APR,MAY...

Richmond, this works for me. on mouseUp put the topStack into STAKK if (the short name of this stack) is STAKK or STAKK is empty then answer "activate the target stack first" with "Ok" exit mouseUp end if answer file "Select image:" if the result is not cancel then set the lockscreen to true set the...

Hi David, What I see is fields with vertical scrollbars and probably a group with a vertical scroll bar. Those take the "motif" look on web (html) since there are no translations to web apps. Livecode provides new controls that look good on web like PolyList and PolyGrid. They look the same as in th...

Hi David,

Could you specifiy what kind of scrollbar you need. I did some scrollbars for "web" exactly for the reason you cite.

Maybe a small screenshot of the scrollbar you have in mind?

Kind regards
Bernd

Thanks Mark for this generous offer.

There are many gems inside those. Even if you only use the Script Profiling feature to test your code for bottlenecks it is well worth downloading those stacks.

Kind regards
Bernd

Craig, in case you want to try to change 'actionPaste': -- more code textEndGroup set the backColor of char tFrom to tFrom + length(the clipboardData["text"]) of field "Script" of me to "yellow" ## add this line unlock screen end actionPaste It sets the backColor, if you want to paste repeatedly you...

@Dunbarx, You would probably like to look at handler actionPaste in stack "com.livecode.scripteditor.behavior.editorcommon" For me the easiest is to open the stack via the Properties Inspector with "Show IDE Stacks in Lists" turned on. Whatever you do it will probably confuse the Script Editor. Kind...

Hi Stam, Thanks for making this very nifty and useful widget. As does the tabKey handler (although I'm not sure why lockMessages is needed - but hey, if it works I'm not questioning it :) and more importantly does not stop the fieldAction message from being emitted which was my concern). Try to remo...

Hi Stam, I am embarrassed that I did not read your reply carefully, I was in a hurry, sorry about that. Re tabbing out: it works if you have the placeholder text showing but not when there is text in the text field. It is probably a matter of taste whether you should be able to tab out of your text ...

bn wrote: ↑

Mon Dec 18, 2023 3:44 pm

Those the important changes that set traversalOn working right while the widget is build.
Also when placing the widget on a new stack.
They might cure your woes...

You made no mention of it so I thought you might have overlooked them.
Kind regards
Bernd

Hi Stam, If you want the user to be able to tab out of the widget add on tabKey lock messages pass tabKey unlock messages end tabKey Seems to work without untoward effects in short testing. Please note that if it is a password field then the moving of "placeholder text" is visible behind the right s...

Hi Stam, change handler setTraversalOn to command setTraversalOn set the traversalOn of the owner of me to the widgetTraversalOn of me end setTraversalOn There is something going on with referencing in Script Widgets https://quality.livecode.com/show_bug.cgi?id=24455 change handler openControl to on...

Here is a stack that simplifies setting the loc of a scaled stack. I has a handler 'setLocation' that is generic enough to be used in other projects (button 'setLoc') After Stam's very useful explanation and sample stack at the beginning of this topic I figured that a simple way to handle moving sca...

Hi Stam, as far as I understand this: on mobile the keyboard pops up in certain situations and the deveoper might want to move things around in that situation. Hence it is for mobile since this does not happen on desktop Working screenrect is the permanently available area of the screen. Effective a...

I'm not sure I understand how the effective screenRect is different from the screenRect though... Would it be appropriate to include this tidbit in the screenRect's dictionary entry? The actual text in Description of this entry is a bit laconic and perhaps impenetrable to new users... As with many ...