Long Running Designer Problem
Just about every developer I talk to complains about the 'Find' feature in Designer that more often than not causes the Designer to crash. Advanced find seems to crash most of the time whilst the basic find crashes on all but the simplest of projects. The fact that this feature only works on those projects where it is least required seems to make the 'Find' feature fairly pointless.
This issue has been around since the early versions of v9 and I would have expected OT to have fixed this bug by now (unless someone can tell me it's fixed in 9.2 onwards). In the meantime we have to ensure that we save before hitting 'Find' and resorting to using text editors for searching source code.
Have OT got any news on a likely fix for this?, and will this be available for earlier versions of Designer?
Comments
-
I agree, It's a pretty shocking bug that has plagued V9 since release. I've got to the point that I no longer touch it because it's so useless and liable to crashing!
Any finding / replacing that I now need to do is managed through Notepad++ and a search through the files contained within the solution. It's actually more useful in other areas too because the validation error messages that are supposed to link back to components is equally useless and often point nowhere.
Explaining all of this to developers at new customer sites is just embarrassing as it should be regarded as basic functionality!
0 -
Just thought I'd check this as I may have been avoiding it unnecessarily but when testing on a customers 9.1.2.6 environment it still fails but not with the big red cross that I expected but instead when scrolling or sorting the result set .
This error and the fact that the result set includes most items multiple times over doesn't create the most convincing impression of the product or that it can be relied upon - how can we be sure that everything is displayed - and indeed is replaced if we dare step that far?
TITLE: Designer Error
------------------------------An unexpected error has occurred within the Designer. Contact your support representative with the extended information in this message.
------------------------------
ADDITIONAL INFORMATION:Property accessor 'Location' on object 'Metastorm.Ide.FindAndReplace.FindResultsControl+FindResultDataBindItem' threw the following exception:'Cannot get a name path, an object in the tree has a null name' (System)
------------------------------
Cannot get a name path, an object in the tree has a null name (Metastorm.Common.Metamodel)
------------------------------
BUTTONS:Continue
Quit
------------------------------0 -
We found 9.1.3.6 had most of these issues fixed. We cannot use it because of issues in Oracle, however, but the find function works well.
0
Categories
- All Categories
- 123 Developer Announcements
- 54 Articles
- 152 General Questions
- 148 Thrust Services
- 57 Developer Hackathon
- 37 Thrust Studio
- 20.6K Analytics
- 4.2K AppWorks
- 9K Extended ECM
- 918 Core Messaging
- 84 Digital Asset Management
- 9.4K Documentum
- 32 eDOCS
- 190 Exstream
- 39.8K TeamSite
- 1.7K Web Experience Management
- 10 XM Fax
- Follow Categories