Previously I've steered clear of using selectInput in a library. However I recently created a rather
trivial library that supports the pixelation of images via cfdg (CF3), so I thought I would use selectInput for the sake of simplicity.
My experience with both processing-1.5.1 and processing 2.0a6 on linux (both Kubuntu and Aptosid) is that I need to avoid selecting files from history (as initially offered by the system file manager) since this completely freezes the application. However if instead I select a file from a folder application, it works OK. Has anyone else had similar experience, what's it like on Mac & Windows?
Now this isn't a big issue for me, but for the casual user of a library like mine this is quite counter-inuitive. However if there isn't a problem on Mac or Windows (ie the majority of users) then I would prefer to use selectInput rather write my own file handler as I have before.
PS I don't think issue has anything to do with my using selectInput in a library that's why this is a programming question.
My experience with both processing-1.5.1 and processing 2.0a6 on linux (both Kubuntu and Aptosid) is that I need to avoid selecting files from history (as initially offered by the system file manager) since this completely freezes the application. However if instead I select a file from a folder application, it works OK. Has anyone else had similar experience, what's it like on Mac & Windows?
Now this isn't a big issue for me, but for the casual user of a library like mine this is quite counter-inuitive. However if there isn't a problem on Mac or Windows (ie the majority of users) then I would prefer to use selectInput rather write my own file handler as I have before.
PS I don't think issue has anything to do with my using selectInput in a library that's why this is a programming question.
1
