The freedesktop.org menus are the most complex out of all operating systems out there, and wine goes through a laborious process to make them.
Removing them is not simple. I believe wine does remove the .lnk files in ~/.wine/drive_c/windows/start menu and such, but the mapping between .lnk files and freedesktop menus is currently one-way.
A while back I thought up a scheme where explorer monitors the .lnk menus and the freedesktop menus and syncs them in real-time. But there are more problems, like if you delete a freedesktop menu it will be recreated as long as the .lnk file is there, unless you keep another list of created menus and don't create a freedesktop menu twice, but you have to keep track of .lnk deletions and remove from that list...
The freedesktop.org menus are the most complex out of all operating systems out there, and wine goes through a laborious process to make them.
Removing them is not simple. I believe wine does remove the .lnk files in ~/.wine/ drive_c/ windows/ start menu and such, but the mapping between .lnk files and freedesktop menus is currently one-way.
A while back I thought up a scheme where explorer monitors the .lnk menus and the freedesktop menus and syncs them in real-time. But there are more problems, like if you delete a freedesktop menu it will be recreated as long as the .lnk file is there, unless you keep another list of created menus and don't create a freedesktop menu twice, but you have to keep track of .lnk deletions and remove from that list...
Yes, it's an incredible amount of work.