On Tue, Jun 17, 2008 at 3:51 PM, Ed Leafe <[EMAIL PROTECTED]> wrote: > On Jun 17, 2008, at 5:27 PM, Nate Lowrie wrote: > >> I am just hoping for the day when I am not finding them anymore. > > The Class Designer is a very complex application, and I'm the only > one working on it. Up until now it only improves when I create an app > that uses it; now that you're using it, it's good that you're finding > these things. > >> If I am in the Class Designer and change the method name in the >> editor, the >> method name is not changed in the selection even after I save it. >> Even if I close it and reopen it the name hasn't changed. below is >> the sample HTML for the part in question: >> >> <_getSearchFields><![CDATA[ >> def _getSearchFieldChoices(self): >> return self.SearchFieldEntry.Choices >> ]]> > > I debated (with myself) whether to make the editor a single page for > all methods, or set it up to edit one method at a time. I chose the > latter because that would enable entering the method signature > automatically. > > Currently the code doesn't check if you modify the method name inside > the editor, mainly because it never occurred to me that someone would > do that!
Guess it's all part of the may different ways to do something. My way to try to get around the renaming issue. > >> I have not figured out how to rename or delete methods. Can I do this >> without delving into the code and doing it by hand? The delete method >> is very important. I thought that if I just deleted what I had in the > > > If you cut all the code for a method, and then switch to another > method, that method is deleted. IOW, empty methods are not kept. You > can then create a new method with your new name, and paste in the old > code (deleting the old def line, of course). Got it. I noticed this happened after I sent the email and was futzing with it some more. I guess that will be standard OP, though I still think that that renaming the method in the editor window should change the name of the method in the method list. > >> I just have one more thing that I wanted to mention. In using the >> ClassDesigner these past couple of weeks, I have become somewhat >> annoyed by all of the possible event and object methods being >> displayed in the editor dropdown. It makes it hard to know which ones >> are defined and saved and which ones are blank. > > Non-empty methods have an asterisk by their name. They are also > sorted to the top automatically. Ahh...Now this one threw me for a loop. I originally thought that the asterick was to symbolize they were not saved. I see now. That is pretty cool, though I would have probably still been wondering if you hadn't told me. > >> I guess I would like to see only defined methods appear in that list >> and have the option >> for all the standard methods in a dropdown list in the new method >> dialog. Thoughts. > > > I guess I have a different concept of "defined". Example: > 'afterInit()' is defined for all classes, but by default is empty. > > This seems like a very minor point, and not one worth spending time on. It is very minor and just a preference thing. I was more concerned about it before I realized that the Non-empty methods are auto-sorted to the top. Nate L. _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/[EMAIL PROTECTED]
