Implemented the unit tests and the functions needed for the JavaScript to work.
The buttons along with the animations are now working, but still have a grey field above them since I can only use them when I click "Show Forms". I'll tackle them next.
| aacid |
| Okular |
Implemented the unit tests and the functions needed for the JavaScript to work.
The buttons along with the animations are now working, but still have a grey field above them since I can only use them when I click "Show Forms". I'll tackle them next.
Open this file:
http://www.texample.net/media/tikz/examples/PDF/animated-set-intersection.pdf
Any animations on this:
http://www.texample.net/tikz/examples/tag/animations/
should work, including the one with buttons.
| No Linters Available |
| No Unit Test Coverage |
| Buildable 12475 | |
| Build 12493: arc lint + arc unit |
| core/script/kjs_document.cpp | ||
|---|---|---|
| 276 | Please use a range-based for loop. | |
| core/script/kjs_document.cpp | ||
|---|---|---|
| 138 | you don't need this anymore? | |
| core/script/kjs_document.cpp | ||
|---|---|---|
| 275–286 | This convoluted for loop basically get the i-th element of a QLinkedList, which is not designed for index accessing (and that is why there is no at(int) method).
| |
| core/script/kjs_display.cpp | ||
|---|---|---|
| 20 | Are we talking about the std::unique_ptr? I followed the template in the other classes, why should we use unique_ptr? | |
| 36–39 | Then we get rid of the initialized bool? | |
| 41 | And this does not compile | |
| core/script/kjs_document.cpp | ||
| 275–286 | I still have to check for all the pages. But my new implementation looks more like with what you described | |
| core/script/kjs_display.cpp | ||
|---|---|---|
| 36–39 | Yep, also unique_ptr will clear the allocated memory, if you run valgrind, it will point a leak which is not good. | |
| core/script/kjs_display.cpp | ||
|---|---|---|
| 41 | g_displayProto needs to be a std::unique_ptr for this to compile. | |
I intend to test this when all the functions needed to work are implemented.
Or would you like a test for every function?
Having as much test coverage as possible is the best. If you think you need some more building blocks for this to be more easily autotestable, that's also a valid answer
Implemented setInterval/clearInterval. WidgetScripts are now supported on pageOpening/Closing.
The diff shown here is wrong. We want the diff from your branch against master, not the last change in your branch against itself