Grd project does now work with latest SVN

[GoogleCodeExporter]

What steps will reproduce the problem?

1.while trying to use grd project tool wih a grd opened. 

What is the expected output? What do you see instead?

the geographic computator window does not automatically find the # of 
lines in memory. nor it allows feeding manually.

What version of the product are you using? On what operating system?

latest SVN

Please provide any additional information below.

 see attached image

Original issue reported on code.google.com by rrama...@gmail.com on 11 Mar 2008 at 10:47

Attachments:

• grd_project_no_lines.jpg

[GoogleCodeExporter]

Strange, I cannot reproduce that behavior. Does it happen using a particular 
grid 
type?

I just updated the grdproject mex. This hopefully corrects a new feature were 
Mirone 
would hang on a second call to grdproject. 

Original comment by jl...@ualg.pt on 11 Mar 2008 at 7:35

[GoogleCodeExporter]

Dear Joaquim,
Thanks for clearing the issue 5. Now it is opening and saving goes through 
correctly.
But this grdproject error is still there. the grd file I attached for issue 5 
do 
show this and so are other grd files. another matlab version tangle?!
cheers
-rajaraman

Original comment by rrama...@gmail.com on 13 Mar 2008 at 3:56

[GoogleCodeExporter]

Nope, it still works fine here with R2006b.
You will have to debug it on your side. Please try this.
Put a break point on line 205 of geog_calculator.m. From your error case m and 
n 
should show up as zeros. Now the question is why?
handles.gridLeft is assigned at line 54. Is it empty there? That should only 
occur 
when ... IS IT IT?
what is your "Grid max size"?

Original comment by jl...@ualg.pt on 13 Mar 2008 at 7:44

[GoogleCodeExporter]

Oops!
There you are! The grid max size in preference is 0 instead of the default 
300MB.
Once I changed it, grdproject is working fine.
Thanks a lot
-rajaraman

Original comment by rrama...@gmail.com on 14 Mar 2008 at 4:40

[GoogleCodeExporter]

OK, Added a test to warn user on situations where array was not in memory due 
to a 
small "Grid max size" 

Original comment by jl...@ualg.pt on 16 Mar 2008 at 11:25

• Changed state: Fixed