Hello, I've made a little testing to the latest svn version. Here are my observations: - pausing the simulation doesn't work -- fixed that - bug of messing up circuits still exists; I can't trigger it reliably, but moving a component / changing something and reloading the circuit triggers it sometimes. The big problem is that the involved code related to these operations is really messy. (maybe it should be rewritten :P) I'm thinking of implementing some kind of logging functionality to track this. From what I've tested, the corruption doesn't happen due to incorrect loading -- the saved data correspons to the corrupted circuit.
minor annoyances: - led's color is always gray, changing it has no effect - simulator: connecting a source to a fixed voltage. they don't add up (there are lots of such quirks...) - oscilloscope: doesn't scale well: if a quantity (example: current) changes too little, only a horizontal line can be seen instead of the waveform - some components have no icon on the toolbar - coudn't change the direction of the pins by dragging the pins - also managed to crash ktechlab by closing an assembler document My question is: how should we track the bugs? Just enumerating them here isn't really useful. Zoltan ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Ktechlab-devel mailing list Ktechlab-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ktechlab-devel
