Timeline
Jun 1, 2021:
- 4:18 PM Ticket #3825 ($tagEDITSTREAM definition is wrong in Beta 3.3.15.3 when using x64) updated by
- Based on a few tests I made, I believe the right definitions are : […] Notice the align 4 on the last 2 tags starts after the tagNMHDR struct
- 6:44 AM Ticket #3825 ($tagEDITSTREAM definition is wrong in Beta 3.3.15.3 when using x64) updated by
- Hi, richedit structure are very special You got the wrong behavior for $tagEDITSTREAM They are other $tag... that can be wrong too if the UDF's that use them use extra field not aligned to 4 $tagGETTEXTEX ptr lpDefaultChar;ptr lpbUsedDefChar" $tagMSGFILTER wparam wParam;lparam lParam" $tagENLINK wparam wParam;lparam lParam;" & $tagCHARRANGE can you verified if they need to be fixed too ? Thanks for the help
May 30, 2021:
- 5:53 PM Ticket #3825 ($tagEDITSTREAM definition is wrong in Beta 3.3.15.3 when using x64) updated by
- Just create any Test.rtf document. And use beta. […]
May 25, 2021:
- 7:58 AM Ticket #3822 (Helpfile for MsgBox: Comment for return values TRY AGAIN and CONTINUE ...) updated by
-
Owner, Resolution, Milestone changed
Changed by revision [12542] in version: 3.3.15.4
May 24, 2021:
- 10:28 AM Ticket #3822 (Helpfile for MsgBox: Comment for return values TRY AGAIN and CONTINUE ...) closed by
- Works For Me
- 9:38 AM Ticket #3823 (Helpfile: Language Reference - Variables: Section Arrays and Maps ...) closed by
- Fixed: Fixed by revision [12541] in version: 3.3.15.4
- 9:29 AM Ticket #3824 (_GUICtrlRichEdit_StreamFromFile help file error on default character ...) closed by
- Fixed: Fixed by revision [12540] in version: 3.3.15.4
- 9:17 AM Ticket #3824 (_GUICtrlRichEdit_StreamFromFile help file error on default character ...) updated by
- Not true it can read UTF8 file as it is usung the default reading mode But it is true that if the file is ansi it is the same as default UTF8 I will change the doc to $FO_READ Thanks
- 9:06 AM Ticket #3825 ($tagEDITSTREAM definition is wrong in Beta 3.3.15.3 when using x64) updated by
- Unless the MSDN doc is wrong there is no error Can you give a repro script ? Thanks
May 23, 2021:
- 8:51 PM Ticket #3822 (Helpfile for MsgBox: Comment for return values TRY AGAIN and CONTINUE ...) updated by
- Yes, I'm happy :-) Thanks a lot. water
May 20, 2021:
- 2:07 PM Ticket #3825 ($tagEDITSTREAM definition is wrong in Beta 3.3.15.3 when using x64) created by
- It should be reverted back to the actual 3.3.14.5 version : […] …
- 1:59 PM Ticket #3824 (_GUICtrlRichEdit_StreamFromFile help file error on default character ...) created by
- Help file says that _GUICtrlRichEdit_StreamFromFile character encoding …
- 12:45 PM Ticket #3822 (Helpfile for MsgBox: Comment for return values TRY AGAIN and CONTINUE ...) updated by
- You have add the correct flag to get any of the buttons to appear - I see no need for a note in this particular case. 3.3.14.0 (10th July, 2015) (Release) Minimum OS requirements are now Windows XP SP3 and Windows Server 2003 SP2 So these buttons will appear on any version of Windows on which AutoIt will currently run. So the double asterisks appear unnecessary and should be removed. Happy? M23
- 10:42 AM Ticket #3822 (Helpfile for MsgBox: Comment for return values TRY AGAIN and CONTINUE ...) updated by
- You have to use flag $MB_CANCELTRYCONTINUE to get this return values. So the footnote might be something like this: "Try Again" and "Continue" are returned when parameter flag is set to $MB_CANCELTRYCONTINUE. This only works on Windows 2000/XP and above
- 10:16 AM Ticket #3823 (Helpfile: Language Reference - Variables: Section Arrays and Maps ...) created by
- Helpfile: Language Reference - Variables: Section Arrays and Maps. …
- 10:08 AM Ticket #3822 (Helpfile for MsgBox: Comment for return values TRY AGAIN and CONTINUE ...) created by
- There is a footnote marker for the return values TRY AGAIN and …
May 10, 2021:
- 4:56 AM Ticket #2170 (_ArrayDisplay fails handling arrays with no elements) updated by
- WGJW9 - MQBRH - C3VXP - DB6PF - M89P3
May 6, 2021:
- 4:46 PM Ticket #3821 (_WinAPI_OemToChar should be forced to ASCII) closed by
- Fixed: Fixed by revision [12536] in version: 3.3.15.4
- 4:41 PM Ticket #3821 (_WinAPI_OemToChar should be forced to ASCII) updated by
- Not sure the title is the right way to describe that when using _WinAPI_OemToChar() with string greater than 65536 a crash occurs The pb is the same for _WinAPI_CharToOem() the right solution is […]
May 4, 2021:
- 7:39 PM Ticket #3821 (_WinAPI_OemToChar should be forced to ASCII) updated by
- https://www.autoitscript.com/forum/topic/205736-solved-how-to-write-special-characters-to-scite-editor-moved/?do=findComment&comment=1481251 The proposed change, does not solve the issue.
- 4:55 PM Ticket #3821 (_WinAPI_OemToChar should be forced to ASCII) created by
- As per this thread : …
Note:
See TracTimeline
for information about the timeline view.
