matplotlib and wxPython are clashing? about oscaar HOT 9 CLOSED

I will take a look. I think I know what's going wrong, just by reading your comment; I had this issue once as well.

Edit: Can't run differentialPhotometry.py atm, see the new issue threads.

from oscaar.

Btw: If you didn't change it, and you have matplotlib v 1.0.0 or higher, plt.ion() is on for plt.* by default. For me if I use it again, together with plt.show(), I get frozen windows and all of weird things.

from oscaar.

@dmgaldi : could you please turn off the part of the OSCAAR GUI that keeps open the "loading please wait" display, and have the gui.py script terminate wxPython windows once the differentialPhotometry.py script has been triggered?

I think wxPython and matplotlib aren't playing nice together. If it turns out that this is indeed the problem, I will go ahead and create the matplotlib-based status bar that I talked about.

from oscaar.

Brett,

Okay, it should be taken care of.

-Dan

On Mon, Mar 4, 2013 at 11:58 PM, Brett Morris [email protected]:

@dmgaldi https://github.com/dmgaldi : could you please turn off the
part of the OSCAAR GUI that keeps open the "loading please wait" display,
and have the gui.py script terminate wxPython windows once the
differentialPhotometry.py script has been triggered?

I think wxPython and matplotlib aren't playing nice together. If it turns
out that this is indeed the problem, I will go ahead and create the
matplotlib-based status bar that I talked about.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/32#issuecomment-14423569
.

from oscaar.

In my last commit I fixed the problem. I had been having issues on my machine because the "homeDir()" method used the string "\\" as the splitting point in the path to get to the main oscaar directory. Does anyone's computer use that (@dmgaldi)? For me, the path's dirs are separated by "/" ( ie /usr/bin, not \\usr\\bin). I've changed the "homeDir()" method accordingly.

from oscaar.

My 2 minutes of Wikipedia-ing [path formats turned up this](http://en.wikipedia.org/wiki/Path_(computing\)). It looks like we should safely be able to assume that / is the appropriate character for path splitting.

from oscaar.

Brett,

I'm currently working on windows and os.getcwd() returns directory names
separated by "". I thought this was a windows thing so I thought I put a
sys.platform check. When I'm in Linux they are separated by "/". We should
get Sam to try it on his windows machine.

-Dan

On Tue, Mar 5, 2013 at 10:39 AM, Brett Morris [email protected]:

In my last commit I fixed the problem. I had been having issues on my
machine because the "homeDir()" method used the string "" as the
splitting point in the path to get to the main oscaar directory. Does
anyone's computer use that (@dmgaldi https://github.com/dmgaldi)? For
me, the path's are separated by "/". I've changed the "homeDir()" method
accordingly.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/32#issuecomment-14446101
.

from oscaar.

@SamTheGeek : you've been summoned.

from oscaar.

@SamTheGeek : Never mind.
@dmgaldi : I've found a solution. The os.sep command returns the string that is used as the separator between path components on a given machine. Change the "\\" or "/" that we've been fighting over to os.sep and it will work.

from oscaar.