copy pages to combine panel projects

Hello.

Copy Pape, Paste Page.

When copying pages as described above, programming still disappears.

Projects are not listed in the project tree like shown above, but in tabs.

I also tried merging the project that I wanted to copy a page from by dragging one tab to the other, but that results in error "Project can't be merged to itself. Please select another project".  Why?

So I like to repeat Jos his question of 2 years ago: How can I copy a page from one project to another WITHOUT losing all programming on the items?     Nb: both projects do share the same server project.

Hello.

Bindings in "Programming" are not carried over when copying and pasting pages. Each project has its own set of drivers, even if they are copies of the same project. Attach your projects, specify which page and from which project you want to copy to another. We will try to find a solution for your case.

So, the answer you gave to Jos 2 years ago was incorrect.

For the project I was working on, I now already re-did all the programming manually. But it is really annoying this has to be done manually everytime you copy some page, or just some items from one project to the other.

Hello.

2 years ago, a method was specified for copying pages with all the graphic elements from one project to another. The "Programming" bindings were never migrated when copying. It is pointless to transfer them in this way. If you need bindings, you need to create a copy of the project, remove all matching pages, popups, drivers from the copy, and make a Merge.

Then you will get the pages in the new project, the driver with the same bindings.

Hi Vladimir, thanks for trying to explain.

But, as I told the dutch Iridium representative a few times : documentation is not up-to-date and/or incomplete. And even your answer above is outdated.

The original question of Jos was: "can somebody tell me how i can copy pages to another panel project without losing the programming" and he was told just to use copy+paste.   This was not correct.

So the work around is merging projects. That will keep the programming in place.

But like I wrote above: "Projects are not listed in the project tree like shown above, but in tabs."

But still you give me an example with a project-tree? I don't understand. This leads to confusion.

I found out myself (not in the manual!) that merging projects is now done by dragging one tab onto another.

This should be in the manual.

When I merge my 2 projects this way, Iridium Studio tells me:

Why does Studio think these projects are the same? How do I tell Studio they are not te same?

Can you attach yours to the 2 projects you are trying to merge? This way we can figure it out faster. If your projects contain confidential information, then open a private ticket by referring to this discussion (attach a link to it).

Maybe I have found the answer my self. In the Project.irp files I found ProjectGUID="F1EFD9B3-8B77-43E6-BDCA-3BE1E730C835".   This number is the same for all projects I have.

Could this be what Studio is looking at when deciding all of my projects are the same?

Yes, it is.

Resaving the project under a different name doesn't fix this? If it doesn't fix it, what version of the studio is used?

Just tested: No, using Save Project as does not fix this. The ProjectGUID stays the same and merging is not possible.

Last 2 years I have always used the latest updates of Iridium.

At this moment:

iRidium Environment: 1.3.25.0.23561

iRidium Studio: 2.0.15.23561 (64 bit)

Transfer: 1.1.3.14538 (32 bit)

iRidium: 1.3.25.23561 (64 bit)

Server: 1.3.25.23561 (32 bit)

iRidium lite: 1.3.13.19977 (32 bit)

Server lite: 1.3.13.19977 (32 bit)

Try creating a new project, don't add anything to it, and merge it with one of the projects. The remaining two projects can be successfully merged.

Yes, that's a good workaround. The empty project with the merged old project has a new ProjectGUID :-)

Hello.

1) You can't merge the project with itself anyway, since the project GUID is the same, even after saving.
2) The restriction on the project GUID that does not change after Save As is not a bug.
3) This restriction was enforced, since not only the project GUID is the same in the project, but all drivers and commands and tags will have the same GUIDs when they are installed, this cannot be allowed.
4) The old studio allowed you to do this, and so you often encountered synchronization errors in the case of identical HWIDs and edited projects manually. This is not right, so the new studio rejected it.