On May 30, 2012, at 9:24 AM, David Lonie wrote: >> I think in this case, the treeview should be either empty (possibly >> displaying some helpful message that the relevant data files could not >> be found instead), or the menu item should be greyed out/not exist at >> all.
I'll look into this. Naturally, there's a similar issue with the fragments code, and shortly the polymer builder as well. > Or, it wouldn't be to hard to add a variable to a configured header so that > the extension could look in the source tree if the installed location doesn't > exist. Geoff would know more about the extension, lets see what he thinks. I think both things are important -- disable the menu item when no files are available. My concern about the source tree is knowing where that is. I'm not sure I want to compile-in the source directory. Should I know that it was compiled by /home/mbanck/avogadro/... ? -Geoff ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Avogadro-devel mailing list Avogadro-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/avogadro-devel
