https://bugs.freedesktop.org/show_bug.cgi?id=82641
--- Comment #10 from Michael Meeks <[email protected]> --- Hi there, > 2. After that I read through the source code of NumberFormatPropertyPanel.cxx > which implements the current Button. AFAIK this code implements only the > handler for the button. (makes sense for me) Ah ! in my logs, I would expect to see a file of a few thousand lines - with cut/paste portions of the text, and notes on call-stacks from the debugger when this file was hit, along with speculation on what each method does, and your assumptions listed etc. to form some sort of (not beautiful, not so readable - but very information dense) log of what you're thinking while code-reading that. "I read some more code." To me is a journal you wrote afterwards, not a dump of your scratch-pad of interesting bits of code you read along the way that may (or may not) be related. Again - you cannot possibly hope to work in this model: until (understood) { read-code -----> store in mind } ... now I know what to do ... ... write code ... This is simply going to fail; always. I am proposing you this model: until (understood) { read / edit existing notes until (sub-problems-understood) { read-code ---> write notes if (too-complex) { break into new sub-problems : things I don't understand. assume certain sub-problems have various results: -> write notes on the assumptions you made here } else // fully understood write notes on the sub-problem solution & remove from the list. } ... go home, sleep, wake-up ... } ... design a fix ... ... hack on this ... > This is where I stuck because of the concept of signal, slots and other > stuff. (don't understand the implementation and dependencies of the > current button) Ok - so we went around this loop once. This is good progress; now we know what we do not know - so - store the state of what you had learned up to now - and all those code pointers; and recurse - now you have a much easier problem: what is a signal / slot - how does that work ? what code can you read to understand and write notes on that ? ... > I don't know where I should start with the implementation of the custom > widget and how to get rid of the old button. Ah - but you can't know everything; you can only learn some good techniques of systematically reducing problems to smaller ones, and then solving those. The smartest person in the world cannot keep all of this in their head, and put it together: so giving up on that is prolly a good step #1 ;-) -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
