ronen1n Posts: 10 19/06/2024	ronen1n Posts: 10 Hi Sometimes I update software faster then the updater by extracting the portable app and changing the version file number, but then the updater tells me to update to version 5 from 6 example: 5.0.0.sps.version to 6.0.0.sps.version
	link
Gianluca Administrator Posts: 1290 19/06/2024	Gianluca Administrator Posts: 1290 Yes, you are right. SyMenu is not able to read in a reliable way a program version. In fact sometimes the program version is the same as the executable version but often it is not. The only way SyMenu has to safely know a program version is trusting on the SPS infrastructure i.e. on its own update system. For every program managed by the SPS system, SyMenu creates a placeholder file called something like 24.06.sps.version where naturally the first part is the current program version. This is the only way SyMenu has to track the current version of a program. If you want to update a program before SPS does, you should move your program folder outside the SPS main folder (SPSSuite\SyMenuSuite) to prevent the collision and the notification. Or accept the fact you will update the program again when available on the SPS system. Or you can manually edit the placeholder file name modifying the version part with the version SyMenu wants to move with the update. I hope everything is clear now otherwise, please, ask.
	link
B0ne Posts: 3 3 days ago	B0ne Posts: 3 Hello everyone, I also have a question or a suggestion for improvement on this topic: it would be great if you could exclude programs from the update in the updater. As far as I can see, this is not yet possible. Currently (18.01.2025), for example, the updater wants to update the “Joplin” program from version 3.1.24 to 3.2.10. In my opinion, however, this is a mistake, because the last stable version is 3.1.24; version 3.2.10, on the other hand, is still in the beta phase. So I'm currently ignoring this update (it won't work anyway), but it would be nicer if I could simply prevent the update as I said. This would also solve ronen1n's problem. PS: many thanks for Symenu and all the work that went into it
	link
B0ne Posts: 3 3 days ago	B0ne Posts: 3 In the meantime, my statement is no longer correct: Joplin v3.2.11 is currently the stable version. But that doesn't change my suggestion...
	link
Gianluca Administrator Posts: 1290 3 days ago	Gianluca Administrator Posts: 1290 B0ne wrote: [...] it would be nicer if I could simply prevent the update I agree with you... It could be a really nice update. I've got an idea that IMHO can work very well. SyMenu decides when a program needs to be updated by checking a special file you can find in every root program folder: it's called "x.y.z.sps.version". This file is empty but its name contains the version for the current program. So for example if Joplin is updated at version 3.2.11, the file will be named "3.2.11.sps.version". This raw and crude system is needed because it is really difficult to check a version program from the executable itself (I've already spoken about this problem so I won't repeat myself) and because SyMenu really needs to know the current program version to suggest there's an update on the way. So SyMenu can make available a function called "ignore this version". When you apply it to a certain SPS, the program won't be reported as updatable until the next version. Unfortunately SyMenu doesn't have a local DB where it can track this kind of data because it works only with physical files so the only way I have to implement this feature is to leverage the "x.y.z.sps.version" file. How? Simply when the user chooses to "ignore this version" I can rename the file with the available version that needs to be ignored. This way SyMenu thinks the program is updated and won't suggest there's a new package for it, but the program remains at the previous version. It's not a great solution because it implies a misalignment between what the SyMenu thinks about that program and the real program version. Anyway it fixes the problem with a little effort on my part and an easy interaction for the user. What do you think about that?
	link
B0ne Posts: 3 2 days ago	B0ne Posts: 3 Dear Gian, thank you very much for your answer. I am actually already using your workaround exactly as you described. I believe you have already described the purpose of these files here in the forum, so the trick with the *.sps.version files was obvious. What I didn't know was that Symenu doesn't have a local db. But then of course you are right, my suggestion will hardly work without db. I'll just continue to make do as before by renaming the .sps.version files. Have a nice day!
	link

---