> Is it not simpler to not limit extensions, just offer '*' / '*.*'? > > IMO, adding user or 3rd party (non-free) specific extensions > hard-wired into hbide (or any Harbour code) is very bad idea. > > Of course another more complicated way is to make this configurable > (f.e. via hbide.ini). >
I agree. > AFAIR this has been implemented, and now you can call > 'hbide my.hbp' to launch a project. > > Adding necessary file type association is left as a job > for users, as it's highly platform dependent and some > users may not like such tampering in local environment. I'll investigate. Maybe the feature is yet available. Any clue about how to implement the file association? TIA Maurizio _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
