that looks good. I was hesitating about adding this because I was pondering how to best display parameter and values as tables.
But this might work just as well. We'll have to see how it works with LCB dictionary. LCB dictionary makes heavy use of tabular display.
Interestingly "Field" (object) has more entries in Livecode Dictionary than in the community dictionary.

Gee, and I thought my code was so convoluted that it was kind of encrypted..

Could you please use strict compilation mode for code changes i.e. declare all variables, thank you. And also please prepend your local variables with t and script local variables with s. That way it the scope of the variale is immediately obvious.

Yes, it took a little time to find the script and then work out what you were doing.

Here is an update. Seems "value" can be the end of a line as well as heading.
Changed the heading to "Values"
Given that each section is identified by the offset of ["heading" & cr] it is possible that any lines ending with one of the heading words, preceding the respective heading, will upset the formatting for that heading. In the case I just fixed a preceding line ended with the characters "value" and so the lineoffset of ["value" & cr] found that line and not the heading, which was later on.

I have adjusted the variables as requested and declared them, turned on strict compilation mode to ensure.

BTW the "Field" object entry has an extra section called "Property" which is a listing of all properties of the object. This is not in the field.ldoc. It is also not in the array entry for "Field <object>" so it must get generated by LC's dictionary. I notice that other "objects" have the Property table too.

to keep the versions in sync I post here a version that incorporates the changes James Hale made i.e. he added Parameter and Value to the dictionary.

Additionally this version has minor bug fixes and a collapse/expand option. In the search bar there is an icon with a - minus sign which collapses the dictionary. Currently only hard coded into widget "toggleSize" -> the one with the minus sign. You would have to change it there if you want the collapsed dictionary to appear somewhere else.

Hi Bernd,
Yes I was worried that might happen. After I made the corrections I looked at the field object entries. Should have posted first
Anyway, trust you got my point about the current method of identifying the section heading. Might need a tweak'?
Also I am pretty sure the <object> entries must trigger an extra handler that collates all the property entries that have the <object> mentioned. This would not be difficult to do, but it would be a bugger to try and format without a table. Maybe just listing the properties (as links) would be enough?

Hi Bernd and others dictionary workers,
Thanks a lot for your work.
I just dowloaded "DictionarySplitter_0_7_6_2".
First feeling is very nice. Simple, clear, shrink/expand dictionary is very useful.
Remains an important question "where is the best place for "DarkTheme" button
Kind regards
Jean-Marc

Last edited by jmburnod on Fri Mar 10, 2017 7:28 am, edited 1 time in total.

How could we add to this Dictionary all confirmed bugs and workarounds?

where is that information coming from? Or do you mean user notes that the user maintains himself.

@Mikey, I am exploring the option of user notes. But this is in early stages and needs some consideration. Since tinyDictionary currently is only the empty stack and the dictionary is pulled from the current version of LiveCode and only preferences are saved externally. A user notes system has to be fairly robust and reliable and also stored externally. Imagine the user notes get somehow corrupted. I would not like to answer that support question if it turns out that it was a bug I did not catch.

The current release of this stack (with user notes!) is now available on livecodeshare.
you can access from within LC by clicking on the "Sample Stascks" button in the toolbar or you can go to the livecodeshare site:http://livecodeshare.runrev.com/stack/8 ... Dictionary

Hi Bernd, Sorry for replying so late, but I lost track of this message thread

bn wrote:@Alejandro, what do you mean by: How could we add to this Dictionary all confirmed bugs and workarounds? Where is that information coming from? Or do you mean user notes that the user maintains himself.

[[ I've come across this issue before when LiveCode was present in the "Security"section of System preferences.

To test, Go to "System Preferences--->Security & Privacy--->Privacy" and in the tab "Accessibility" check that LiveCode is **not** present in the section "Allow the apps below to control your computer"

I tested this tonight and when LiveCode is in here, it takes between 15- 30 secs for the file dialog to appear and my system locks up until it shows. ]]

I just tried this and I confirm his findings.

Could you please check if this improves the problem for you?

Best regards,
Panos

This is exactly the kind of information that I am talking about.
A really useful addition that could be included in this Dictionary.