BUG in classparser?

[Oliver Eichler]

Am Don, 27 Jan 2000 schrieben Sie:
> Hi,
> after a second look there is effectively a problem with the dialog editor but 
> I don't think that it is related to his other problem with the out of sync
> classview.  
> By the way the classview is not directly updated on compilation but for every
> save and when you click on View->Refresh
> 

Yes, so far I bypassed the problem by getting the class tree in sync
with saving/compiling & refreshing the class view. After doing so I
had no problems with the dialog editor anymore. What would the dialog
editor do if it can't find the correct line-in-file to place it's
code? Would it stop? Or would it continue and corrupt the code? I
guess the first, as it didn't corrupt my code sofar.  Thinking about it
the class view to line-in-file mapping database should be updated at
following occasions:

*after a save
*after/before/during compile
*before adding a method/variable
*before the dialog editor is entering it's code
*any other occasion..?

BTW: The autogenration of methods and data via class tree is wacky,
too. I suspect the same reason. Sometimes a privat variable is entered
into the protected section. Sometimes a new 'private' section is
opened, and so on... Keeping me busy updating the calss view manualy ;)

oliver

-- 
Ingenieure Kellermann, Voigt, Hoepfl, Eichler und Weidner 

DSP Solutions                  http://www.dspsolutions.de