![]() |
WP cache function bug
Ok, here's a new thread on this topic (to make KWo happy ;) ):
The Wp cache function doesn't work properly: 1) The # of the cached Wp isn't shown correctly (shows some loong number like "199643331" instead - well, something similar. You get the idea.) 2) The WP cache isn't emptied. Once cached, a WP stays in cache until the whole game is restarted. There are two possible solutions: 1) Auto-clean the cache after one add/delete operation (disadvantage: when deleting a bi-directional connection, you need to cache 2 times) 2) Add an option to clean WP cache anytime you like (disadvantage: more complicated to code, I guess, and maybe not enough numbers free in WP menu?) ------- @PMB: Thanks for the effort you made to save SF's and my precious little waypointing fingers from rheumatism - you're like a mother (only that most moms don't code as well...) :D [in reply to your last comment in the "ladder bug" thread] |
Re: WP cache function bug
Quote:
OK - back to the thread - I just copy what I said in ladder bug thread. Many times I cached some wp, and after I tryied remove some connection and I saw the situations: a) message Already no Path to this Waypoint b) deleting of some another connection , not to cached wp. Similar problems with adding path to some cached wp. BTW: In Bots-United there is an off-topic forum, but for all bots. Maybe we have to ask SF and PMB to open an off-topic subforum at PODBOT26mm forum? Here is really like in chat-room...:) Oops - maybe I should write this at Ideas subforum? :D |
Re: WP cache function bug
I think I've just found the problem to this bug..
Code:
UTIL_HostPrint ("Waypoint #%d has been put into memory\n"); Code:
UTIL_HostPrint ("Waypoint #%d has been put into memory\n", g_iCachedWaypoint); |
Re: WP cache function bug
Ok, reading code is like reading a Chinese newspaper for me... but if I guess correctly, the change you show here will only correct the message displayed on screen when caching a WP, but not the problem with the cache not being emptied, or am I wrong?
|
Re: WP cache function bug
you have to empty it yourself by going to an area of no waypoints and trying to cache one
|
Re: WP cache function bug
Yes - You have to do it in this way, because something is missing in the code. Look here:
http://forums.bots-united.com/showthread.php?t=1518 there is described: Quote:
|
Re: WP cache function bug
in the code it doesn't seem to clear it after you use it..
do you guys want it to be cleared after it's been used? |
Re: WP cache function bug
Quote:
a) what about deleting bi-directional connection (You can still leave in memory this cached WP for this man wanting clear connection in second direction, but if he will not do it - the cache will be not cleared)? b) if somebody wants to add to cached WP1 another WP3, after connecting WP2 - in this case he has to go once again to this WP1 (cached at begining for first connection) to make connection between WP1 and WP3 - maybe somebody likes this way - cache once and after make manualy all connection to this first cached WP? I think - You have to ask directly SoUlFaThEr - this function was made by PMB especially for him and T Wrecks (You remember this post about save their fingers... ;)) - we can't decide something different. T Wrecks wrote his opinion - now wait for SF. |
Re: WP cache function bug
Well, to be honest, I think a solution where the menu entry "Cache this WP" would change to "Clear WP cache" whenever a waypoint is in cache, would be the absolutely fabulous kick-ass solution.
Two other solutions are the one that empties the cache automatically (with all the advantages / disadvantages described by me & KWo) and, of course, the one that's in the code right now. The only problem I had with the current solution is that I didn't know it! ;) I'd say this is very low-priority anyway, so I wouldn't insist on changing it now. In the long run, the solution I described here might be the nicest one, but I can work very well with the function as it is now - now I know it! |
Re: WP cache function bug
it seems to be the most logical solution T Clear WP Cache...simple and smart.
|
All times are GMT +2. The time now is 08:50. |
Powered by vBulletin® Version 3.8.2
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.