Boring delays after several prozesses

Peter Engels shared this idea 10 years ago
Gathering feedback

Hello, did you ever think about shortening the delaytime after a process has finished successfull?


Esp. While importing caches via GC code the long delaytime after a successfull import is really boring.


Sometimes I want to import several caches via GC and after every import i have to wait until I can import the next one.


I think 1 sec displaytime is enough.


But after all, this is a great app, it was really worth the money.


Peter

Replies (2)

photo
0

Good day Peter,


I`m not 100% sure that I have same experience as you. What means "long delays"? You see for a longer time some loading wheel etc?


What if you for example want to add one simple point into some point folder? Is this also take some time? If so, you have Locus on your card or internal memory (isn`t card really slow)?

photo
0

I try to explain (I have German language)


Via "Geocaching for Locus", I choose "import GC", then I enter the GC code.


Then Locus asks to what folder to import ect...


after selecting "import" the import starts.


After the import has finished there is shown a Messagebox which tells that there was 1 PIO imported (and the number of waypoints)


This message (splash screen) stays ~ 4 secs, and think this time can be shortened. 1 sec should be enough.


If the time is shorter, it is possible to import several GCs faster than now.


(also all other success messages should be shown in a shorter time, as I think only Error-messages are really important enough to be shown a longer time)


I hope this clarifies


Peter

Leave a Comment
 
Attach a file