summaryrefslogtreecommitdiffstats
path: root/tests
Commit message (Collapse)AuthorAgeFilesLines
* Remove test-cases added [ac48fb2d729f3994|here]: This test-case gives ↵jan.nijtmans2021-11-011-8/+0
| | | | different results in 8.6, which are fixed in 8.7
* Test-case cleanup (all backported form 8.7)jan.nijtmans2021-10-318-669/+677
|
* TIP 608 implementation - Add <<TkWorldChanged>> virtual eventgriffin2021-10-221-0/+141
|\
| * Possible fix for tkticket 3049518 - Generate <<TkWorldChanged>> event.griffin2021-08-041-0/+141
| |
* | Fix [489b69a820]: Slightly wrong error message on 'wm attributes $w -junk'fvogel2021-09-142-8/+3
| |
* | Add new test textIndex-19.14 for [934cab5005]. This test does not fail with ↵fvogel2021-09-121-0/+12
|/ | | | the legacy text widget but fails with revised_text.
* Remove comment which is not true any more. Some more formattingjan.nijtmans2021-05-311-2/+2
|
* Be more tolerant about timing in tk-6.5 and remove unneeded constraint. This ↵fvogel2021-05-241-4/+2
| | | | test really does pass on macOS with XQuartz. It may fail (both with XQuartz or with aqua) because of the slowness of the continuous integration platform on which the tests are performed.
* Fix [ff9c815a83]: 8 Aqua unixWm tests fail if the dock is positioned on the ↵culler2021-04-301-12/+15
| | | | left side. Also fixes a segfault at exit in ximage.c.
* Fix textWind.test à la François Vogelculler2021-04-291-10/+10
|
* Add a call to [window display] after creating a new window. This makes the ↵marc_culler2021-04-292-230/+233
| | | | tests work in High Sierra.
* Deal with new test failures revealed by changing the order of the tests.culler2021-04-283-15/+33
|
* Merge 8.6culler2021-04-275-13/+25
|\
| * Adjust textWind-17.10culler2021-04-271-12/+16
| |
| * Using the CALayer changes some timings -- make some small adjustments to a ↵culler2021-04-254-6/+12
| | | | | | | | few tests to avoid sporadic timing-related failures.
| * Add calls to update idletasks in scale-20.7 and scale-20.8.culler2021-04-251-0/+2
| |
* | Backport stabilization of event-9 from 8.7fvogel2021-04-261-0/+3
| |
* | merge core-8-6-branchfvogel2021-04-245-7/+83
|\ \ | |/
| * Fix [ea876b3e8a]: Text peer widget ignores set -startline when scrolling ↵fvogel2021-04-182-2/+17
| |\ | | | | | | | | | with the scrollbar.
| | * Augment test text-32.3 so that it fails if previous commit is backed out.fvogel2021-04-171-2/+2
| | |
| | * Add non-regression test textDisp-11.22fvogel2021-04-131-0/+15
| | |
| * | Fix [34db75c0ac]: Text peer widget error on Down arrow key when passed ↵fvogel2021-04-182-0/+48
| |\ \ | | | | | | | | | | | | -endline line. Also, propagate the fix for [1630271fff] from marks to embedded images and windows.
| | * | Slightly simplify test textMark-6.6fvogel2021-04-181-2/+1
| | | |
| | * | Remove extra empty line.fvogel2021-04-181-1/+0
| | | |
| | * | Extend textIndex-26.2 to tags located outside -startline/-endlinefvogel2021-04-181-5/+9
| | | |
| | * | Fix syntax error in textIndex-26.2 testcase.fvogel2021-04-181-1/+1
| | | |
| | * | Trying to get the index of an embedded image or window should trigger an ↵fvogel2021-04-181-2/+18
| | |/ | | | | | | | | | error when located outside of -startline/-endline (same as for marks, this was bug [1630271fff]).
| | * Let the newly introduced test textIndex-26.1 also test the -startline condition.fvogel2021-04-121-1/+6
| | |
| | * Add non-regression test textIndex-26.1fvogel2021-04-111-0/+13
| | |
| | * Add non-regression test textMark-6.6 (failing before the fix, passing with ↵fvogel2021-04-101-0/+12
| | | | | | | | | | | | the fix)
| * | Fix [3540e4929cd]: Revised [text]: textDisp-17.10 fails. The tests of the ↵fvogel2021-04-171-1/+17
| |/ | | | | | | TkTextScanCmd procedure combine xview, yview and scan commands, and typically check what is the resulting index @0,0. However, the text widget updates its view at idle time, and the tests shall take this fact into account, otherwise the results may be linked between tests. Especially textDisp-17.9 has wrong expected result (see also commit [bf453137e1]).
| * Use "tkwait visibility" to stabilize the testcasejan.nijtmans2021-03-251-4/+1
| |
* | merge core-8-6-branchfvogel2021-03-224-2/+40
|\ \ | |/
| * Stabilize tests event-9 and textTag-16.2. See [9e1312f32c].fvogel2021-03-222-1/+7
| |\
| | * Add a comment in event-9 and let GitActions run one more time.fvogel2021-03-211-0/+2
| | |
| | * Another trivial change, let the GitHub action run again.fvogel2021-03-191-0/+1
| | |
| | * Once more. Backout previous trivial change, and let GitActions run again.fvogel2021-03-181-1/+1
| | |
| | * Once more. Make a trivial change (add a space character in the textTag.test ↵fvogel2021-03-171-1/+1
| | | | | | | | | | | | file) just to let GitActions run again.
| | * Backout previous trivial change, and let GitActions run again.fvogel2021-03-161-1/+1
| | |
| | * Make a trivial change (add a space character in the textTag.test file) just ↵fvogel2021-03-151-1/+1
| | | | | | | | | | | | to let GitActions run again.
| | * textTag-16.2: Try an update after configuring the 'big' tag, even if the tag ↵fvogel2021-03-141-3/+2
| | | | | | | | | | | | is not yet applied to anything.
| | * Try Jan's suggestion for event-9: Maybe the update after the pack has a ↵fvogel2021-03-131-4/+3
| | | | | | | | | | | | timing issue. What if the pack isn't fully handled yet (in Windows UI thread), so the warp doesn't find the frame it's warping to? So putting some waiting time before this update might help.
| | * If this still allows event-9 and/or textTag-16.2 to fail, then it cannot be ↵fvogel2021-03-092-3/+7
| | | | | | | | | | | | a timing issue.
| | * <u>event-9</u>: Try an increase of the waiting time. fvogel2021-03-082-11/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <u>textTag-16.2</u>: For each of the following environnements : * My Win10 at home (PASS) * GitHub action (msvc) (PASS) * GitHub action (gcc(all)) (FAIL) * GitHub action (gcc(mem)) (PASS) the debug output produced by the previous commit is always the same, independently of the PASS or FAIL test result : Courier 12 -family {Courier New} -size 12 -weight normal -slant roman -underline 0 -overstrike 0 -ascent 14 -descent 4 -linespace 18 -fixed 1 Helvetica 24 -family Arial -size 24 -weight normal -slant roman -underline 0 -overstrike 0 -ascent 29 -descent 7 -linespace 36 -fixed 0 17,29 -- 27,47 Conclusion: this is not a font issue. Let's try a different timing test then.
| | * Some debug info in an attempt to understand what's going on with ↵fvogel2021-03-061-0/+8
| | | | | | | | | | | | textTag-16.2 (font issue?)
| | * Experimentfvogel2021-03-042-2/+3
| | |
| * | Fix [9b6065d1fd]: Tk doesn't restore overwritten Tcl command "update"jan.nijtmans2021-03-191-0/+33
| |\ \
| | * \ Merge 8.7jan.nijtmans2021-03-165-7/+10
| | |\ \
| | | * \ Merge 8.6jan.nijtmans2021-03-151-2/+2
| | | |\ \ | | |_|/ / | |/| | |
| | | * | Fix [2374c602bf]: bind-34.1 sometimes fails on Linux.fvogel2021-03-131-3/+3
| | | |\ \
generated by cgit v0.12 at 2025-09-11 21:27:52 (GMT)