SET AS RECORDING TARGET seems capable of being a PROJECT that is not open . . .

mbatchelor

All --

I had two PROJECTS open within PREMIER.  Lets call them A and B.

I removed PROJECT A and PROJECT B from the PREMIER then I added EXISTING PROJECT C.

I started working on PROJECT C without specifically performing a

    SET AS RECORDING TARGET

to set the CODE of PROJECT C.

As part of that work, I did a RECORD MACRO.

PROBLEM . . .

PREMIER opened one of the files associated with PROJECT A and recorded the macro in that module.

I am ABSOLUTELY SURE that I had not set a PROJECT A module as the RECORDING TARGET while it was open but after the RECORD MACRO, the PROJECT was open within PREMIER again.

It seems that PREMIER chose one of the modules of PROJECT A as a RECORDING TARGET (even though it was closed) based on some logic that I cannot follow.

Can someone please follow up on this and determine whether this is PILOT ERROR (beyond just forgetting to SET A RECORDING TARGET) or whether this is GLITCH that needs some TLC?

Thanks.

-- Matt

PierreD

Matt,

Thanks for reporting this, I checked with the latest code which will be released with the next version of Premier and it's behaving appropriately, so the issue will be addressed in Premier 9.2.

Pierre

mbatchelor

Pierre --

Super.

Sorry slow to CLOSE this QUESTION / DISCUSSION.

Thanks.

-- Matt