| Commit | Date | |
|---|---|---|
|
[r4429]
by
david_costanzo
Fix a bug in CURRENTWORKINGDIRECTORY that broke under cygwin's bash This revision changes the implementation of CURRENTWORKINGDIRECTORY to use DLLCALL for ::GetCurrentDirectoryA instead of invoking perl.exe as an external process. The problem with perl is that I had installed cygwin's perl and FMSLogo was finding it. This returned a cygwin path ("/cygdrive/c instead" of "c:\"), which caused the test code to fail to CHDIR back to that directory. As a result, running DIRECTORYTEST moved out of the "test" directory, which caused strange, difficult-to-understand downstream failures. Since it's now possible to use DLLCALL to call get the working directory, it makes sense to do so. |
2017-07-31 11:08:29 | Tree |
|
[r4428]
by
david_costanzo
Rename SEARCH_OPERATION_FindAndReplace to SEARCH_OPERATION_ReplaceAndFind. |
2017-07-30 16:21:08 | Tree |
| 2017-07-30 16:10:25 | Tree | |
| 2017-07-30 05:42:56 | Tree | |
|
[r4425]
by
david_costanzo
Fix Bug #499; When a single widget is added to a dialog or window from the setup instructionlist, it no longer fills the entire dialog/window. This was a regression introduced in FMSLogo 7.0.0 caused by upgrading wxWidgets from 2.8.12 to 3.1.0. In this upgrade, there was a bug fix in wxWidgets that made it behave this way (that it, it was always supposed to do so, but it so happened than in 2.8.12 it didn't due to a bug). The fix for the FMSLogo bug is to add a sizer to all wxDialog that are created with WINDOWCREATE or DIALOGCREATE. This disable the "single widget fills all space" behavior in wxWidgets. |
2017-07-30 05:15:07 | Tree |
| 2017-07-09 22:45:22 | Tree | |
| 2017-07-09 22:42:15 | Tree | |
|
[r4422]
by
david_costanzo
Ban procedure documentation from starting with "This", as in This was done for documentation-wide consistency. |
2017-07-09 22:11:52 | Tree |
|
[r4421]
by
david_costanzo
Clarify what was meant by "The start position is always on the same ellipse, regardless of startangle". When I read this recently, I couldn't understand what it meant or how the following sentence was explaining it. Instead of combining to unrelated ideas ("start position" and "same ellipse"), I removed the "same ellipse" explanation from the startangle description and added it as a conclusion to the inline/crosswise paragraph. |
2017-07-09 16:19:31 | Tree |
| 2017-07-09 14:56:16 | Tree |