LiveCode Forums

I only tested the workaround in 9 - mainly on Linux.

There is code (handlers) to go to the next/previous row/cell (one for each direction). When navigating that way, tabs are automatically inserted. My guess is that something is amiss with the calculation of tabs that need to get inserted when clicking on an arbitrary cell. The location is good in one...

Looking at the code, I can see why arrow keys work. Knowing that should make finding a solution easier. I kind of doubt that it is random, I’m guessing there will be a pattern too.

Vertical does work after you switch tabs a few times. (Still a bug, but there is a work around). The listed bug report is something that I’ve taken a look at. The proposed logic is pretty much what is used, but for some reason the initial resize permission isn’t getting set correctly (there is a set...

My comment was more for how to generate a widget that works for both. If you distribute with both lcm files then it would work fine. If you initially compile in 9, then it uses lcm, you only get the 2.lcm when there is already a lcm for 8 (v1 of lcm format). Agree that a commercial widget needs to o...

The release of LC 9 fixed the recompile issue. What you need to do is update the source code and install in LC 8. When you launch LC 9 it will recompile the widget for LC 9 but leave the working code for LC 8 as long as the lcb file is present. The files are "module.lcm" and "module.2.lcm"

I think it just needs one or both of these handlers (probably just the first one): public handler OnSave(out rProperties as Array) put the empty array into rProperties return rProperties end handler public handler OnLoad(in pProperties as Array) end handler When I added them, I was able to save the ...

I’m sure there are a few that would look at the code to help track down where the issues are.

The advantage is that you don't have to manually load/save the values. Look at the "my" entries in the LCB dictionary. Not all of the properties that you listed are covered. Color is probably the easiest example. Standard color settings are available within the widget (my background paint, my border...

You need to read the value of the property and then adjust your code accordingly. Those properties are just values, it is up to your code to give them meaning as appropriate for your widget.

I think it will depend on the size of the team and the size of the project. If you have multiple pieces of GUI that you can separate out into multiple stacks so that you can split out work on those pieces, then Levure would fit that model. If you have one person that will be the traffic cop for the ...

To do this would require a pretty significant change to the widget. The underlying data is an array so the value is either a string or an array. Keys are sorted alpha or numeric. You could probably use 2 part keys (sort ID,key name) and adjust the code to sort by the ID and display the key name. I’l...

The first release of 9.1 will have my PR included which disables the autocorrect on the dictionary search field. Easy to include in your own copy if you want:
https://github.com/livecode/livecode-ide/pull/1969

Ok. I’ll pull up a widget and do another test.