Claus Pedersen
Member³
First of all, thanks a lot for introducing the warning message "This object is owned by a different user. Continue compilation anyway?".
I have sometimes tried to make changes to a package on a test schema, and switched to the production schema (in the same PLD session) to check some data, go back to the package and make some more changes and press F8 to compile. The result: the package has been compiled on the production schema with all the problem this causes. This situation will hopefully be less frequent in the future with this new warning.
But: when I open a file in a schema and right after change to another schema and compile the file on the new schema, I also get the warning. This time it should not pop up, because the file was never compiled on the first schema. It is always good to warned maybe one time too many, but it is a little confusing
I have sometimes tried to make changes to a package on a test schema, and switched to the production schema (in the same PLD session) to check some data, go back to the package and make some more changes and press F8 to compile. The result: the package has been compiled on the production schema with all the problem this causes. This situation will hopefully be less frequent in the future with this new warning.
But: when I open a file in a schema and right after change to another schema and compile the file on the new schema, I also get the warning. This time it should not pop up, because the file was never compiled on the first schema. It is always good to warned maybe one time too many, but it is a little confusing
