Misunderstanding when the same name of arguments are used in two different procedures

Bugs and Other Issues
1

Hi.
I have an app with two procedures so similar to each other, that I probably copied the first one "FactPas", and renamed the second "FactCondBorraNodOfr" (Or maybe they first used global variables and then I changed to arguments, I don't remember by now).
The case is both procedures have several arguments to receive some input data, and their names remained the same ("Lat" and "Lon", short for Latitude and Longitude).

Today I just discovered that If the app first execute one of the procedures, and then the other. The second time it keeps for the arguments the same input data of the procedure executed first, instead of taking the data of the arguments sent to the second procedure.
¿Does someone have experimented something similar?

I'm trying to overcome the issue by renamig the arguments of the second procedure to "Lati" and "Long".
I hope to make a car travel tomorrow and chek if now the app behaves well.
Best regards and happy hollidays.

2

It would really help if you provided a screenshot of your relevant blocks, so we can see what you are trying to do, and where the problem may be.

To get an image of your blocks, right click in the Blocks Editor and select "Download Blocks as Image". You might want to use an image editor to crop etc. if required. Then post it here in the community.

Taifun

Trying to push the limits! Snippets, Tutorials and Extensions from Pura Vida Apps by icon24 Taifun.

1 Like
3

Sorry, my dear Taifun.

It's an app too big and complicated, that responds to the inputs coming from other app in a travelling car.

Only comparing the logs from all apps, I finally discovered what really happened

The communication with the app in the car was temporarily lost, and the other app used for the second procedure the last known position of the car (just by the time the first procedure was called).
This lead me to a misunderstanding.

Every thing works fine.

4