Codeproject - Embedding .PNG images into a RichEdit document

[aw27]

I posted the solution to the .PNG Challenge on Code Project.
Every article posted in Code Project has to be approved by members above a certain level.
Assembly Language articles take longer to be approved because most experts have no expertise at all in ASM.
In addition, during the submission phase, I have to deal with comments like this:
"Why have you done this Assembly language? If you wanted low-level you could do it in C". A bit painful.  :shock:

Here is the link:
https://www.codeproject.com/Articles/1360569/Embedding-PNG-images-into-a-RichEdit-document

[daydreamer]

I posted the solution to the .PNG Challenge on Code Project.
Every article posted in Code Project has to be approved by members above a certain level.
Assembly Language articles take longer to be approved because most experts have no expertise at all in ASM.
In addition, during the submission phase, I have to deal with comments like this:
"Why have you done this Assembly language? If you wanted low-level you could do it in C". A bit painful.  :shock:

Here is the link:
https://www.codeproject.com/Articles/1360569/Embedding-PNG-images-into-a-RichEdit-document

great work :t
we C a more skilled and unique coder because he dare to use masm

[hutch--]

Its a good article Jose but you will have to improve that photo.  :P

[aw27]

Thank you all.

I believe the photo is eye catching, so you noticed it. 

[jj2007]

LinkedIn notified me this morning about the article :t
I wonder whether EM_INSERTIMAGE works under Windows 7 with the Office versions of RichEd20.dll. Will test it if I find the time.

[TimoVJL]

Hardly, it don't even support RichEdit50W, as it have RichEdit60W

EDIT: Office 2013 have v8 and RichEdit50W, but works only with RichEdit60W.

[daydreamer]

My idea is create pics from unicode characters + colorization them and bevel some of them and maybe test other effects too
After that starts a gdi based game

[jj2007]

Timo, Richedit50W is certainly not a problem on Win7.

[aw27]

I got the idea now.

Office 2016 has:
Riched20.dll
File Description: Richedit version 8.0
File Version: 16.0.11328.20068
Product Version: 16.0.11328.20068

I have Office 2019 in one machine but can't see any difference, Microsoft also says:
"Retail versions of Office 2016 C2R and Office 2019
The following information applies to retail versions of Office 2016 C2R and Office 2019, which share the same release dates and version numbers."
Probably Office 365 has innovations but I have not purchased that. However, I believe there is no real innovation at all, the product is stagnated and they are milking the cow as much as possible.

So Murray was talking about the File Description not about version-version.

But let's see Windows 8.0:
Windows 8 has:
Msftedit.dll
File Description: Richedit version 7.5
File Version: 6.2.9200.16657
Product Version: 6.2.9200.16657

But let's see Windows 8.1:
Windows 8.1 has:
Msftedit.dll
File Description: Richedit version 7.5
File Version: 6.3.9600.18818
Product Version: 6.3.9600.18818

What about Windows 10?
msfted.dll
File Description: Rich Text Edit Control 8.5
File version 10.0.17763.1
Product version: 10.0.17763.1

So, someone is drinking too much wine!


On the other hand, Murray is now posting about Richedit 9.0. Where is that one?

[jj2007]

Windows 7-64:

Code Select Expand

5.0  5.50.99.2050    C:\Program Files (x86)\Common Files\Microsoft shared\Office11\RICHED20.DLL
6.0  12.0.678.5000   C:\Program Files (x86)\Common Files\Microsoft shared\OFFICE12\RICHED20.DLL
6.0  14.0.7155.5000  C:\Program Files (x86)\Common Files\Microsoft shared\OFFICE14\RICHED20.DLL
3.1  5.31.23.1230    C:\Windows\System32\riched20.dll
4.1  5.41.21.2510    C:\Windows\System32\msftedit.dll

Where possible, I use the Office12 version. Office11 is ok but some features are missing, Office14 is buggy.

[hutch--]

I have good reason to stick with Rich Edit 2/3, it works from old 32 bit OS versions up to current Win 10 64 bit. I have few aspirations of more complex tasks but if I did it would be a version that was available from Win 7 64 bit upwards.

[aw27]

It's complete now.

Code Select Expand



WINDOWS                            RICHED20.DLL                                                                                          MSFTEDIT.DLL
                                 File Description           File Version     Product Version       Class           Comment             File Description          File Version      Product Version       Class

Windows NT                Rich Text Edit Control v3.0    5.30.23.1200       3.0              RICHEDIT20W                         na                          na                   na
Windows 2000              Rich Text Edit Control v3.0    5.30.23.1227       3.0              RICHEDIT20W                         na                          na                   na
Windows XP                Rich Text Edit Control v3.0    5.30.23.1230       3.0              RICHEDIT20W                         Rich Text Edit Control v4.1 5.41.15.1515         4.1               RICHEDIT50W
Windows Vista             Rich Text Edit Control v3.1    5.31.23.1229       5.0.0.0          RICHEDIT20W                         Rich Text Edit Control v4.1 5.41.21.2509         5.0.0.0           RICHEDIT50W
Windows 7                 Rich Text Edit Control v3.1    5.31.23.1230       3.1              RICHEDIT20W                         Rich Text Edit Control v4.1 5.41.21.2510         4.1               RICHEDIT50W
Windows 8.0               Rich Text Edit Control v3.1    5.31.23.1230       3.1              RICHEDIT20W                         Rich Text Edit Control v7.5 6.2.9200.16657       6.2.9200.16657    RICHEDIT50W
Windows 8.1               Rich Text Edit Control v3.1    5.31.23.1231       3.1              RICHEDIT20W                         Rich Text Edit Control v7.5 6.3.9600.18818       6.3.9600.18818    RICHEDIT50W
Windows 10                Rich Text Edit Control v3.1    5.31.23.1231       3.1              RICHEDIT20W                         Rich Text Edit Control v8.5 10.0.17763.1         10.0.17763.1      RICHEDIT50W


OFFICE

Office 2002 (Office 10)   Rich Text Edit Control v4.0    5.40.11.2220       4.0              RICHEDIT20W                         na                          na                   na
Office 2003 (Office 11)   Rich Text Edit Control v5.0    5.50.99.2070       5.0              RICHEDIT20W                         na                          na                   na
Office 2007 (Office 12)   RichEdit Version 6.0           12.0.6768.5000     12.0.6768.5000   RICHEDIT60W      +msptls.dll        na                          na                   na
Office 2010 (Office 14)   RichEdit Version 6.0           14.0.7155.5000     14.0.7155.5000   RICHEDIT60W      +msptls.dll        na                          na                   na
Office 2013 (Office 15)   RichEdit Version 8.0           15.0.4599.1000     15.0.4599.1000   RICHEDIT60W      +msptls.dll        na                          na                   na
Office 2016 (Office 16)   RichEdit Version 8.0           16.0.11425.20024   16.0.11425.20024 RICHEDIT60W      +msptls.dll        na                          na                   na
Office 2019 (Office 16)   RichEdit Version 8.0           16.0.11425.20024   16.0.11425.20024 RICHEDIT60W      +msptls.dll        na                          na                   na




No change in versions between Office 2016 and Office 2019, latest updates I got today. Very weird, but I just confirmed that is the way Microsoft is doing it. I have not noticed any difference at all between Office 2016 and Office 2019, except the Splash Screen says 2016 in one and 2019 on the other. But am not a real Office user.

I can't test Riched20.dll versions of Office until I make a 64-bit program because I have no x86 versions of Office.
Actually, my Office 2019 is x86, and it works for the CodeProject demo when I add msptls.dll and class RICHEDIT60W

[daydreamer]

I have good reason to stick with Rich Edit 2/3, it works from old 32 bit OS versions up to current Win 10 64 bit. I have few aspirations of more complex tasks but if I did it would be a version that was available from Win 7 64 bit upwards.

thanks for the info,good for compability reason to stick to a older rich edit,so I can use it from windows 1.0 to the coming windows 3000 :)
I want to get asian rich edit version,it supports IME and vertical unicode characters ala japanese
actually I suspect I have a ml newer version problem,when 16bit coding it annoys me with requiring cs:,ds:,es: with all mov's to memory adresses otherwise it reports error,but my older code I seen I getaway with none of that???

[hutch--]

I have had no problems with rich edit 2/3 in 64 bit Win10. Its good for about 750 meg so its big enough. The last time I wrote 16 bit MASM code was for MS-DOS back in about 1994 so I would be a bit out of date there but if you are going to write bigger that 64k COM you are stuck with segment addressing which I always hated. Unless its a touch of nostalgia or perhaps 16 bit demos, I don't see much reason to write 16 bit real mode code.

Any modern version of rich edit will handle the unicode range so multi lingual editors are no big deal to do and with a late version of Windows, you have the font support as well.

[daydreamer]

I have had no problems with rich edit 2/3 in 64 bit Win10. Its good for about 750 meg so its big enough. The last time I wrote 16 bit MASM code was for MS-DOS back in about 1994 so I would be a bit out of date there but if you are going to write bigger that 64k COM you are stuck with segment addressing which I always hated. Unless its a touch of nostalgia or perhaps 16 bit demos, I don't see much reason to write 16 bit real mode code.

Any modern version of rich edit will handle the unicode range so multi lingual editors are no big deal to do and with a late version of Windows, you have the font support as well.

judge for yourself if its fast enough and read whats my intention with why get away with only 16bit code
http://masm32.com/board/index.php?topic=7324.0

and about unicode,the idea of gdi game based on unicode characters was inspired from discover there is also unicode chess pieces,cards and mahjong pieces on unicode site among all the other pdfs about for arabic,chinese,japanese... and the need to stack mahjong pieces ontop of each other to make a mahjong game

but you need to tell the user to install foreign language packs,needed to use your for example a japanese version of qeditor