SyMenu Forum

SyMenu

 

Gianluca

all messages by user

23/11/2016
Topic:
Mouse Wheel Scroll for Menus

Gianluca
Gianluca
Administrator
This is my mistake. Already solved with the current beta version.

edited by Gianluca on 19/05/2023
23/11/2016
Topic:
Adding PortableApps.com Menu to SyMenu

Gianluca
Gianluca
Administrator
smile In this case I strongly hope that your efforts will be shared among all the SyMenu user. You only have to upload the SPS after creating it.
23/11/2016
Topic:
Adding PortableApps.com Menu to SyMenu

Gianluca
Gianluca
Administrator
Someone reported successfully integration of SyMenu in the company processes... with a fully happy boss.
So don't give up smile
25/11/2016
Topic:
Adding PortableApps.com Menu to SyMenu

Gianluca
Gianluca
Administrator
Hi Scott.

I'm very interested in your report.

The _sps suffix is added to the root folder only.
The portableapps programs have a single root folder that can be named in whatever way and every other resource the program needs are located inside this root.
The Profile folder is created, along with its parent Data folder, during the program first run and contains all the profile related resources. Naturally the Data folder is located inside the root too.

Usually the program doesn't need to navigate under this root folder. Indeed the program never goes under its own folder that is inside the App folder. When it needs to navigate outside its own folder it uses the environment variables pointers which are created to target the folders inside the root again.

So it is really strange that in certain circumstances this rule breaks because of the root folder naming.

Anyway in the past you found some subtle bugs in the procedure so I completely trust your report. If you like please contact me in private to explain better the problem so I can solve it with the next version. BTW it'll probably be released in the next two weeks.
07/12/2016
Topic:
Run as Admin

Gianluca
Gianluca
Administrator
It's in my TODO list since at least one year but it's not a priority so you won't find in this next version and in the next again. Maybe during the 2017... Please be patient.
13/12/2016
Topic:
New SyMenu version 5.07

Gianluca
Gianluca
Administrator
Hi guys.
The 5.07 is finally out and it is a really powerful version.
If you are interested in the version details go here to read the changelog http://www.ugmfree.it/SyMenuDownload.aspx#changelog
Instead with this post I would like to alert you that some breaking changes have been released or are next to be released.

The first new feature concerns the new environment variable management. No more guides to insert only certain variables. Now you can add whatever variable you like, even newly created ones. I advise you to read carefully the manual (http://www.ugmfree.it/SyMenuManual.aspx#SyProgramAdvancedEnvironmentVariables) where I hope the topic can be clarified better. It's a completely new approach so if anyone has suggestions or issues to report we can open a dedicated thread on this.

Another new feature is the resolution for relative paths. Well I admit that the previous solution was a bit weird: the relative path resolution started from the SyMenu root folder while the most natural location was from the root application path. The new behavior is exactly this last one so if anyone used the relative paths resolution, well you have to change your setting. Sorry but I release the beta version exactly to allow you to test this new behavior. Generally SyMenu hates the breaking changes but this time I was forced to introduce it.

The last point is related to the SyMenu command shell. Since it's about to die please test your programs using the new setting because at some point I will remove the option to use the command shell in favor to the Windows'.

That's all.
In the next version I'll focus my attention on increasing the performances during the SPS program definition deploy that today is really painful.

Gianluca
19/12/2016
Topic:
AsfBinWin by Radioactivepages: SPS Version

Gianluca
Gianluca
Administrator
Hi VVV_Easy_Symenu.

My opinion?

If an author doesn't want to allow the automatic download we don't have to find a way to workaround its will, but we can remove it from the SPS Suite.

The SPS Suite is becoming a strong promotional channel for freeware software and we are starting to have some software authors publishing their own software spontaneously in our suite. Two examples for you: http://www.sterjosoft.com and https://www.filevoyager.com

We can surely use third party repository web site. We have a lot that allowing direct download:
http://www.filecluster.com
http://sourceforge.net
http://www.snapfiles.com
https://github.com
http://fossies.org
http://www.softsea.com

If a software web site closes, we can host by our self the original package to prevent its total disappearance.
We can do the same for software really worthy if the license allows the redistribution but I wouldn't use this forum because sometime I have to compress it and some attachments could disappear. If this AsfBinWin is really worthy I can take your SPS by myself and publish the package on a cloud I use for these stubborn software (http://spshost.altervista.org) or you can do that by yourself it's free :-)

But before any further move, my advise is to contact the author and explain the problem.
If he is smart he will want to be part of this and he will solve the problem of automatic download for us.
23/12/2016
Topic:
New SyMenu version 5.07

Gianluca
Gianluca
Administrator
Hi Glenn.

I'm very sorry that the last change has broken all your scripts. I expected something wrong anyway because the paradigm change was really complex.
The intention was to create a simplified system to set the environment variables. The result was great, aside for the working directory management that is bugged.

This is how the programs should work.
The default working directory must be the executable folder one. If you activate the Advanced tab (near the Gesture) and specify a different working dir, this last value is taken and override the default one.
If you have no executable file but command file, like a batch one, the working dir remains the SyMenu root dir. This last behavior is subjected to change if not suitable.
The Working Directory doesn't work as an environment variable (I didn't even know that such an environment variable exists...) but works and can be set with its specific field.
The bottom multi line textbox (Environment Variables) is for changing and setting system and custom environment variables.
You can use these custom environment variables even in the Working Directory fields.

Now the 5.07 version is bugged on the working directory part, but since someone reported to me early, I have a final version almost ready to release.
Anyway since your situation is quite critical, I decided to release this version as a beta one right now.
Test it and if you find something that still doesn't work, let me know ASAP because the final version will be released soon.

This is the link to download the fixed version. Just unpack the zip and replace your SyMenu.exe file with this one.
Link removed. See messages below for the new beta version link.

And please report me any strangeness.

Gian
edited by Gianluca on 27/12/2016
27/12/2016
Topic:
New SyMenu version 5.07

Gianluca
Gianluca
Administrator
@VVV_Easy_Symenu
What you reported about the VBScript is similar to another report regardind the AutoIt au files. I will try to solve them all before the next release.

@Glenn
I tried to find this %WORKING DIRECTORY% instruction in the SyMenu source code but I found nothing... It means I never implemented such a management.
In this thread instead http://www.ugmfree.it/forum/messages.aspx?TopicID=371#post1026 I found that we spoke about the topic but we solved the problem putting a dot inside the working directory field instead.
This last version, the beta one, solves exactly this problem assuming the working directory is the current executable directory by default, so you don't need to put a dot anymore.


Your three points description about the new working directory behavior is misleading so I will make some examples starting from my three points based on the priority and not on the program type.
The priorities for the working directory resolution are:
- the program custom working directory if available
- the program main directory if available
- the SyMenu base dir

Examples.
Add a program item (not Windows Command but program).
Check the flag Output command
Put cmd.exe in the path folder
Execute
Have you got a program custom working directory available? No
Have you got a program main directory available? No, this is a convention I introduced because the right folder for cmd.exe should be C:\Windows\System32. But even Microsoft decides to start the cmd.exe in a different folder, in Windows 10 for example from %UserProfile%, so in SyMenu cmd.exe doesn't have a main directory.
Ok so we arrived at the catch all third point so cmd.exe will be executed from the SyMenu base dir.

Now check the Enable advanced parameters checkbox.
Write C:\ on the Working Directory field
Execute
Have you got a program custom working directory available? Yes it's C:\ so the cmd.exe will be opened on C:\ folder

Now create a batch file in whatever folder and write a simple dir command inside.
Link it to SyMenu creating another program item
Check the flag Output command
Execute
Have you got a program custom working directory available? No
Have you got a program main directory available? Yes a batch file is a real file existing in a real folder so the main directory will be the folder in which you put the batch file.

Now try to check the Enable advanced parameter
Write C:\ on the Working Directory field
Execute
Have you got a program custom working directory available? Yes it's C:\ so the batch file will be executed on the C:\ folder

The batch case is identical to any UI program case.
I hope this finally help to clarify the program otherwise please ask me again.
27/12/2016
Topic:
New SyMenu version 5.07

Gianluca
Gianluca
Administrator
And this is the fixed version for the VVV_Easy_Symenu bug report.
http://www.ugmfree.it/public/SyMenuBeta/SyMenu.5.07.6205.beta.zip
03/01/2017
Topic:
New SyMenu version 5.07

Gianluca
Gianluca
Administrator
Unfortunately Jess, the former SyMenuRun32or64.exe author is no more among us... well nothing too sad... it's now a Linux user :-)
In my opinion the problem with his script resides in these lines:


; Get the parameters
x86 = %Drv%%1%
x64 = %Drv%%2%


In my opinion the code should be written this way:


; Get the parameters
;x86 = %Drv%%1%
;x64 = %Drv%%2%
x86 = %1%
x64 = %2%


Can you try it? If it works can you share the new exe in the forum please?

Thanks.
03/01/2017
Topic:
Autorun 32 or 64 bit version of app

Gianluca
Gianluca
Administrator
Ok I haven't seen that you already solved the problem. Thanks.

My two cents, if someone prefer leaving the SyMenuRun32or64.exe in its own folder (for example ".\ProgramFiles\SyMenuRun32or64"), you can use the ..\ to go down one level to the SyMenu root and then add the relative path to the program to execute.

To stay in your example it's something like this:
"..\SPSSuite\SyMenuSuite\7-Zip_(x86)_sps\7zFM.exe" "..\SPSSuite\SyMenuSuite\7-Zip_(x64)_sps\7zFM.exe"
edited by Gianluca on 03/01/2017
04/01/2017
Topic:
New SyMenu version 5.07

Gianluca
Gianluca
Administrator
1) Yes it's a new feature, there is no option to disable it and the message will be translated in the final version.
The alert is the first step to automatically update the SPS definitions. When this feature is ready, I'll create an option to disable the check or maybe not because it's not an online check but only a date check.
I know the bug. It's due to the year changes but it'll be solved in the final version.

2) I'm still experimenting with the compressed SPS file but I'm almost sure to introduce it in the final version. The definitions update becomes incredibly fast with the zipped SPS because SyMenu doesn't need to write hundred of files inside the _Cache folder but a single file. If you need help to align the SyMenu Published App Track let me know.

The new version should be released within this week.
11/01/2017
Topic:
Defunct menu item indicator

Gianluca
Gianluca
Administrator
It's surely a nice feature.
Currently you have the Scan for unlinked feature that do something similar but you have nothing like you describe.
Apparently the Scan for unlinked is a very fast process so implement it when the menu starts shouldn't create performance issues.
I have to test it better but it's definitely in my TODO list now.
19/01/2017
Topic:
Out of date definitions, can I turn this off?

Gianluca
Gianluca
Administrator
Not yet sorry.
Is the message so disturbing for you? I searched a way not so invasive to give this information but I can think something else if it is annoying
20/01/2017
Topic:
Out of date definitions, can I turn this off?

Gianluca
Gianluca
Administrator
Yes but don't expect it so soon.
Today the most important thing is that people maintain updated their app definitions.
23/01/2017
Topic:
New SyMenu Version 5.09

Gianluca
Gianluca
Administrator
Hi guys.

A new version is out.

I introduced several little improvements and fix. The most noticeable ones are the mouse wheel activation and the mouse hovering feedback on the search results on the contextual menu. So finally all the mouse fan will be happy.

For people using the custom suites they are restored. I removed them from the 5.08 but naturally it wasn't intentional :-)

The execution for programs that need elevation should be fixed too.

Enjoy.
23/01/2017
Topic:
New SyMenu Version 5.09

Gianluca
Gianluca
Administrator
Ok I think this is a record.
A user reported me a little bug in the configuration form.
The save, reset and save and exit buttons are located in the wrong position if your configuration form has been horizontally resized.
To workaround it, please stretch the form width to the minimum size, exit the form, and now the buttons will be located in the right place.
28/01/2017
Topic:
icons folder inflating!!!

Gianluca
Gianluca
Administrator
This feature is simple to implement but it has a really low priority and requires a lot of time. Unfortunately I have to choose what to implement and what don't.

Anyway to partially solve your problem you can follow this advise.
Statistically the most useless icons are the identical ones because among the group you can find one linked and the others unlinked. It takes only a few minutes to kill them all.
Then when you find a program without an icon you can use SyMenu to extract it again.
I had 847 icons before this activity and 570 after. In one minute.

But I have another solution.
SyMenu is extensible and a plugin to delete the unlinked icons will be a really useful one. So if someone wants to try, please contact me in private.
30/01/2017
Topic:
SyMenu Published App Track

Gianluca
Gianluca
Administrator
The plugin folder name is "Plugin".

My two cents on the interaction with SPS Builder topic.
Your b) solution can absolutely work.
As sl23 says it's a matter of changing a bit of fields even in a very old file.
Well the a) solution will be the more logical one because it is always a danger to change an outdated SPS but, if you work with PAT (BTW nice acronym) the way it's thought, you should always point to the _Cache folder under the SyMenu control and there you can't find a year old file.
So I think it could work.

UGMFree © 2002-2024
PayPal BTC TON