copy crash

[sxmn001]

Has anyone else experienced crash at a copy command in a large program?

[watabehj]

It may or may not be related to the above report, but I found that the following program causes crash in Eviews9（64bit-version Standard Edition May 20 Build）:

wfcreate(wf=wf1,page=page1) q 1985 2017
series ycc
group aaa @pcy(ycc)
wfcreate(wf=wf2,page=page2) q 1990 2000
copy wf1::page1\* wf2::page2\

It runs correctly on Eviews8. Interestingly, if you change series name from "ycc" to "ccc", it runs correctly on Eviews9, too.

[EViews Steve]

Great bug find watabehj!

I was able to reproduce and fix this issue in EViews 9. It will be released in the next patch.

For now,if you want to work around the issue, you'll need to name your group to something alphabetically AFTER the series name. So in your program example, call the group zaa.

Steve

[watabehj]

We found another bug which may be related to the above one.
The following program does not execute "pagecopy" of the last line correctly.

wfcreate(wf=wf1,page=page1) q 1985 2017
series ycc
group aaa @pcy(ycc)
pagecopy

However, if you change the third line as "group aaa @pc(ycc)", "pagecopy" of the last line is executed correctly.

[EViews Gareth]

What do you expect the pagecopy command to do there?

[watabehj]

I think all the objects in the current page, i.e. page1, should be copied to the new page by that pagecopy command. I think it is equivalent to dragging the "page1" tab onto the New Page tab. However, if there is a group containing @pcy(something) in the current page, some of the objects are not copied. It is as if copy is interrupted when copying the group object. (You can see that by changing the group name to something alphabetically after the series name.)

[EViews Gareth]

We'll get it fixed.