Opened 14 years ago

Closed 14 years ago

#2311 closed bug (fixed)

Print composer template creates identically named composer items

Reported by: jctull Owned by: mhugent
Priority: major: does not work as expected Milestone: Version 1.4.0
Component: Printing Version: Trunk
Keywords: print composer template naming Cc:
Must Fix for Release: No Platform: All
Platform Version: Awaiting user input: no

Description

If you create a composer item, save it to a template, then load the template again, the composer item name is identical and you compromise access to the two identically named composer items from the "Print Composers" menu item. The new composer item should get an index number appended or some other method of producing a new composer item uniquely named relative to the already existing one.

Currently, you will see and have access to only one of the composer items under the "Print Composers" submenu. You have to go to the "Composer Manager" to be able to access each composer item. You can rename from there to work around the issue manually.

Change History (1)

comment:1 by mhugent, 14 years ago

Resolution: fixed
Status: newclosed

The problem was that, after the template read, the instance has been unregistered from the composers submenu, but not inserted again. Also, I think the composer title should not be changed when reading from template file.

r12612 fixes both issues.

Note: See TracTickets for help on using tickets.