Doing some due diligence on the 0.5 branch I figured I would post here as pictures may help.
Here are the screenies of the KUAL config string errors reports thing.
# Stop following links when looking for json files
KUAL_nofollow="true"
KUAL_nofollow="false"
^-- Wasn't 100% sure how to test this. I am assuming recursive folders could/not contain config files. Will revisit.
# Hide the status line and re-routes status messages to the trail line
#KUAL_no_show_status="true"
Really liked this option and it appears to operate as expected : )
KUAL_show_KUAL_buttons="1 2"
KUAL_show_KUAL_buttons="2 1"
^-- Working to hide kual buttons.
Nice. Order of incidence does not matter. Nor affects button order.
Hides Nicely
(picture 1)
However, as shown in picture 1 any value whatsoever (other than commented out no-value default) causes the new logging button to not appear. Unsure if that is by design. "No value" shows all function options.
(picture 2)
Further testing revealed that the Sort Menu 123 was not actually causing the
sorting to change. Rather than replacing the
#KUAL_options="-s=ABC" with
#KUAL_options="-s=123"
the values were in fact concatenating at the end thusly
#KUAL_options="-s=ABC -s=123 -s=123 -s=123"
# Entries per page - default 10 (KT/PW), 5 (other kindles)
#KUAL_page_size="10"
KUAL_page_size="8"
KUAL_page_size="15"
This appeared to work nicely initially: The counts were indicated in the relevant readout area and buttons counts matched requests.
(pictures 3, 4, 5) 10, 15 and 8 button counts respectively.
However... And I am still not
100% on why.
The KUAL buttons "Replace Store Button" and "Sort Menu Button" now both error with the errors shown
(pictures 6, 7, 8) as you can see I attempted to remove the custom button count and it no longer appears linked to the custom button value but this could be what caused it (I did this directly before noting the now borked buttons)
Note that I was testing SORT MENU above without the "string" error.
(The concat error was exhibiting at that time in it's stead)
I also tried several variation of:
#KUAL_options="-s=ABC"
KUAL_options="-s=ABC"
KUAL_options="-s=123"
which had no effect on the error.
I then totally deleted the KUAL.cfg file and tried the SORT 123 option again.
which worked properly and produced
Quote:
# KUAL.cfg - created on Sat Dec 1 04:22:49 UTC 2012
KUAL_options="-s=123"
|
finally showing me the
Sort Menu ABC button as expected.
(picture 9)
Thus I conclude the error lies
somewhere in the cfg parser itself.
This also fixed the STORE TOGGLE button.
the report was a little "Low" on the readout
(picture 10)
Hope this helps.
I did have a dig around in..
https://bitbucket.org/ixtab/kindlela...e.sh?at=master
To see if I could spot anything obvious. After 3 hours of staring at it I realised I would need another 50 or so hours of staring at it and started this post
EDIT: I attached the "not worky show errors" KUAL.cfg but damned if I can see what is wrong with it.