Ok, it was all just a misunderstanding :-) There is an option in the Domain.xml "update-displayname" that is a config option for the MacroUpdater listener. The value is set to true by default so that for many operations (move included) the displayname is automatically updated to the filename. This was overriding the displaynames I had chosen for my files. I changed it to false and it no longer changes my files during moves etc.
So the answer to my first question is: no, the move method shouldn't normally update the displayname property on a resource unless the Slide server's macro updater listener has been configured to do so in Domain.xml. And, question 2: yes, you must checkout a file if its version controlled and you want to change its properties. At least that seems to be the case but if you disagree or know a way to get around this let me know. Thanks, Warwick > -----Original Message----- > From: Warwick Burrows [mailto:[EMAIL PROTECTED] > Sent: Monday, September 27, 2004 1:47 PM > To: '[EMAIL PROTECTED]' > Subject: Move method changes displayname property? > > > > Hi, > > Should the move method change the displayname property of a > resource during the move? I'm finding that it does. I want > to keep the displayname that I have set for any moved > resources. Is this a defect?? > > BTW, when I try to set displayname on the moved target I get > an error since my resources are under version control. I'm > trying now to checkout the file first and then modify the > displayname property to what it should have been. I am > testing this workaround now and don't even know if it will > work. If it does then that means for every move I will have > to do this which means a checkin/out record and new file > version in the history just because I have to change the > displayname back. Is it the case that you need to checkout/in > the file to change its properties? > > Thanks, > Warwick > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
