Pablo Trabajos wrote:
> the OCAL import dialog had some other serious bugs that forced it to be scraped from the code
The dialog still exists and works in linux and osx builds (in 0.48.x and current trunk) - it's only defunct (missing) in the Windows builds (see bug #174797).
> This is the kind of thing that should be put into a blueprint
Pablo Trabajos wrote:
> the OCAL import dialog had some other serious bugs that forced it to be scraped from the code
The dialog still exists and works in linux and osx builds (in 0.48.x and current trunk) - it's only defunct (missing) in the Windows builds (see bug #174797).
> This is the kind of thing that should be put into a blueprint
Agreed.