[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice-devel
Subject:    kspread development issues
From:       John Dailey <dailey () vt ! edu>
Date:       2002-07-14 5:32:33
[Download RAW message or body]

Just a couple things to throw out for discussion....

Right now there is a bug in the database about copying a row to the clipboard, 
and then trying to paste it in the cell text edit bar.  This crashes KSpread.  
This is caused basically because it pastes a string a few hundred thousand 
characters long into the QLineEdit and the yacc generated code in the 
koscript parser chokes trying to handle it.  
What would be an ideal way to handle this?  How should we limit what the user 
can enter into a cell without preventing them from doing something they might 
need to do.


A while back I added a bit to the error output to indicate circular 
dependancy, parse error, etc... (and those should actually be correct 
now...).  But they look like '####PARSE' and I really wasn't thinking about 
leaving them like that long term.  Although it is at least a little more 
informative than just '####', it's still fairly ugly and not translated.  
Anyone have better ideas?

-John


_______________________________________________
koffice-devel mailing list
koffice-devel@mail.kde.org
http://mail.kde.org/mailman/listinfo/koffice-devel
[prev in list] [next in list] [prev in thread] [next in thread]