the result of the decryption I provided is quite correct and similar to what jigolua offers
get_country_and_state_text is a function which theoretically returns an L"" string
MODEL.address.search.get_country_and_state_text[CALL](string,wstring OUT) - input=string ; output=widestring
in programming 1 or 0 are also equivalent to true or false
we can just as well consider that a null string can be assimilated to false and true otherwise, so the form of the assignment string to boolean does not surprise me, on the other hand in clear text the interpretation can be distorted , all you have to do is correct the expression to perform a transcription
MODEL.lua.AddressSearchStreetsInState = MODEL.address.search.support_streetsearch_in_state(EAddressSearch.Result.selectedCountry) is found in different locations: address.luad , vr_ovde.luad , vr_ovde_search.luad ; et MODEL.lua.AddressSearchStreetsInState is only used inside asc.luad as
if not MODEL.lua.AddressCityIsSelected() and not MODEL.lua.AddressSearchStreetsInState() then
perhaps to solve it would be enough to write
MODEL.lua.AddressSearchStreetsInState = MODEL.address.search.support_streetsearch_in_state(EAddressSearch.Result.selectedCountry) and true or false
if so, it should influence many other similar forms elsewhere
in general when an instruction line is incorrectly formed, the downstream lines of code are ignored or cause the program to crash.
having made a test of this form
MODEL.SET.lua.test = BOOL_MODEL(true)
do
MODEL.lua.test = false
MODEL.lua.test = L"LUA"
sc_InfoMessageBox(tostring(MODEL.lua.test()),1)
end
the dialog box is displayed with the value false and the execution of the line MODEL.lua.test = L"LUA" is ignored
MODEL.lua.AddressSearchStreetsInState = MODEL.address.search.support_streetsearch_in_state(EAddressSearch.Result.selectedCountry) should therefore not require modification
------------------------------------------------------------------------------------------------------------
function sc_ShowSearchAddress(mode) does not exist in this form in the 153810 but has evolved in the following versions. on the other hand I have not found a location in the ui with a button or in the lua of a call to this function
it may therefore be that the apk could have been modified before compilation to use a parameter (mode) while the function in the lua was not updated
it must be taken into account that the scripts in 9.35.2.xxxxxxx show marked differences between them, the teams which develop them are not always the same, it is necessary to look in the corresponding ui to find the info like owners: gkaracsonyi experts: dflajsz
you have to be careful when trying to transcribe elements from one version to another as skinners who take functions from nextgen must do to transpose them into luna, it works but there are limits, that's why I looked at the sources to be as close as possible to the good names of variables and functions.
what can pose a problem is a bad interpretation in the decoding, but from there to miss the complete structure of a function, it is not technically possible, unless you have the wrong source file in the meantime
Bookmarks