Hi all and happy new year!
In FVWM-Crystal, the media menu use auto generated menus for the
playlist and to play individual files.
1) it is a preference dialog where the users can tell Crystal where
their audio and video files are, and write them into a file.
2) from that file, a script generate the menu call into another file.
It use fvwm-directory.
At that time, mine look like this:
DestroyFunc FuncFvwmMenuMovieDirectory
AddToFunc FuncFvwmMenuMovieDirectory
+ I PipeRead 'case \'$0\' in \
"/home/alian/Vídeos"*) myexec="fvwm-crystal.mplayer-wrapper file
dom";;
"/media/Toshiba_External_USB_3.0_20130324040598-1/Backup/Vidéos"*)
myexec="fvwm-crystal.mplayer-wrapper file dom";; "/home/dom/Vídeos"*)
myexec="fvwm-crystal.mplayer-wrapper file dom";;
"/home/dom/Descargas"*) myexec="fvwm-crystal.mplayer-wrapper file
dom";; "/media/cdrom"*) myexec="fvwm-crystal.mplayer-wrapper file
dom";; \ esac; \ fvwm-menu-directory --icon-title
"22x22/categories/directory.png" \ --func="FuncFvwmMenuMovieDirectory"
\ --exec-file "^${myexec}" --dir \'$0\''
DestroyMenu /Music/LoadMovie
AddToMenu /Music/LoadMovie
+ MissingSubmenuFunction FuncFvwmMenuMovieDirectory
+ '%22x22/categories/video_movies_view.png%$[gt.Browse Medias]'
Popup /home/alian/Vídeos
+ '%22x22/categories/video_movies_view.png%$[gt.Browse Medias]'
Popup /media/Toshiba_External_USB_3.0_20130324040598-1/Backup/Vidéos
+ '%22x22/categories/video_movies_view.png%$[gt.Browse Medias]'
Popup /home/dom/Vídeos
+ '%22x22/categories/video_movies_view.png%$[gt.Browse Medias]'
Popup /home/dom/Descargas
+ '%22x22/categories/video_movies_view.png%$[gt.Browse DVD]'
Popup /media/cdrom
4) that file is read by fvwm
As it is here, it work fine. As soon I add things like
--exec-title "^fvwm-crystal.play-movies" or icons into the Piperead
like in Taviso function, fvwm get confused and it fail to open some of
the directories in the Descargas folder and to show the files into them.
It seam like file and directory names with characters like {} or ()
into their names confuse very easily fvwm. At the beginning, I was
thinking it was fvwm-menu-directory that get confused by them, but
after running the same command into a console, it appear the menu
generated by it is correct in any cases. So the issue is in fvwm itself.
I know such characters must be avoided into file names, but they are
broadly used on the internet.
Dominique
