You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
(15) |
Sep
(8) |
Oct
(14) |
Nov
(14) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(3) |
Feb
(1) |
Mar
(12) |
Apr
(11) |
May
(2) |
Jun
(25) |
Jul
(15) |
Aug
(11) |
Sep
(18) |
Oct
(8) |
Nov
(17) |
Dec
|
| 2003 |
Jan
(10) |
Feb
(20) |
Mar
(21) |
Apr
(36) |
May
(14) |
Jun
(4) |
Jul
(11) |
Aug
(3) |
Sep
(17) |
Oct
(26) |
Nov
(6) |
Dec
(1) |
| 2004 |
Jan
(8) |
Feb
(14) |
Mar
(15) |
Apr
(1) |
May
(3) |
Jun
(48) |
Jul
(22) |
Aug
(11) |
Sep
(28) |
Oct
(12) |
Nov
(13) |
Dec
(23) |
| 2005 |
Jan
(19) |
Feb
(14) |
Mar
(38) |
Apr
(46) |
May
(3) |
Jun
(14) |
Jul
(21) |
Aug
(26) |
Sep
(8) |
Oct
(7) |
Nov
(12) |
Dec
(4) |
| 2006 |
Jan
(16) |
Feb
(21) |
Mar
(70) |
Apr
(35) |
May
(42) |
Jun
(16) |
Jul
(16) |
Aug
(8) |
Sep
(2) |
Oct
(9) |
Nov
(14) |
Dec
(3) |
| 2007 |
Jan
(5) |
Feb
(6) |
Mar
(18) |
Apr
(21) |
May
(25) |
Jun
(73) |
Jul
(31) |
Aug
(18) |
Sep
(22) |
Oct
(14) |
Nov
(21) |
Dec
(15) |
| 2008 |
Jan
(3) |
Feb
(2) |
Mar
(6) |
Apr
(10) |
May
(25) |
Jun
|
Jul
|
Aug
(6) |
Sep
|
Oct
|
Nov
(4) |
Dec
(1) |
| 2009 |
Jan
(1) |
Feb
(12) |
Mar
(5) |
Apr
(8) |
May
(10) |
Jun
(7) |
Jul
(29) |
Aug
(14) |
Sep
(6) |
Oct
(24) |
Nov
(14) |
Dec
(7) |
| 2010 |
Jan
(9) |
Feb
(33) |
Mar
(38) |
Apr
(7) |
May
(10) |
Jun
(28) |
Jul
(11) |
Aug
(3) |
Sep
(8) |
Oct
(1) |
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
(3) |
Mar
(7) |
Apr
|
May
|
Jun
(3) |
Jul
(1) |
Aug
(3) |
Sep
|
Oct
(1) |
Nov
(1) |
Dec
(43) |
| 2012 |
Jan
(19) |
Feb
|
Mar
|
Apr
|
May
(10) |
Jun
(1) |
Jul
(7) |
Aug
(1) |
Sep
(4) |
Oct
|
Nov
|
Dec
(1) |
| 2013 |
Jan
|
Feb
|
Mar
(4) |
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(5) |
Dec
|
| 2014 |
Jan
|
Feb
(1) |
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
(2) |
Feb
(1) |
Mar
|
Apr
(1) |
May
(1) |
Jun
(1) |
Jul
|
Aug
(1) |
Sep
(1) |
Oct
|
Nov
|
Dec
(2) |
| 2017 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2018 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2020 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2022 |
Jan
|
Feb
|
Mar
(17) |
Apr
(2) |
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(3) |
Oct
(1) |
Nov
|
Dec
|
|
From: <dam...@lm...> - 2024-10-02 14:33:50
|
The trunk branch is the currently developed version. It used to be 7.1 but then it's version was updated to 8.0 - check this discussion: https://sourceforge.net/p/owlnext/discussion/97177/thread/569a371e2f/ Still unable to get to that thread, I get the FORBIDDEN message. What are the problems you are having with RichEditor? I have been using OWLNext 7.1 until now when I tried to use the released 7.0.14. I have this in my code owl::TCharFormat cf; to fill cf I have this #if OWL_VERSION_16BIT >= 0x0701 cf = myrichedit->GetCharFormat(); #else myrichedit->GetCharFormat(cf); #endif #if OWL_VERSION_16BIT >= 0x0701 mylf = cf.GetFont(); #else cf.SetFontInfo(mylf); #endif #if OWL_VERSION_16BIT >= 0x0701 m_DefaultColor = cf.GetBkColor(); #else m_DefaultColor = cf.GetBkColor(); #endif mylf.lfHeight = 14; strcpy(mylf.lfFaceName, "Letter Gothic"); #if OWL_VERSION_16BIT >= 0x0701 cf.SetFont(mylf); #else cf.GetFontInfo(mylf); #endif myrichedit->SetCharFormat(cf); At this point myrichedit is ready. To print a green colored line I do this #if OWL_VERSION_16BIT < 0x0701 TCharFormat cf(*myrichedit); //a local copy cf.GetFontInfo(mylf); #endif cf.SetBkColor(TColor(0,255,0)); myrichedit->SetCharFormat(cf); myrichedit->Insert(msgtext); This all seems to work well with 7.1. The problem happens when I try to use 7.0.14. With 7.0.14, the same calls give compile errors. From what I could learn, I had to do a Little differently as you can see in the above code where filling cf and mylf are different. When I do the second part to print the colored line, the font is right but the green is Not there. Looking at your richedit example, I see that you create a local cf with the TCharFormat cf(*myrichedit); constructor. With that added local cf, the text background Is green as expected. The question is why can't I use the cf that is already filled by GetCharFormat? What it seems to come down to is this: with 7.0.14 the cf obtained by GetCharFormat Doesn’t work with the background color but the cf obtained by TCharFormat cf(*myrichedit); Works. Also with the local constructor method I have to set the font each time. Damon Register |
|
From: Damon R. <dam...@be...> - 2024-09-29 20:47:21
|
On 9/24/2024 01:32, Jogy via OWLNext-users wrote: > 7.0 is considered the currently stable production version. > > The trunk branch is the currently developed version. It used to be 7.1 but then it's version was updated to 8.0 - check this discussion: > https://sourceforge.net/p/owlnext/discussion/97177/thread/569a371e2f/ Thanks for your reply. it is too bad that its not still on this list. I created a sourceforge account and logged in. I clicked on that discussion thread link and got this Forbidden Sorry, the permissions for this page don't allow you to access it. Browse Open Source Software <https://sourceforge.net/directory/> or Browse Business Software and Services <https://sourceforge.net/software/> > What are the problems you are having with RichEditor? The main problem that I am having is with background color setting. I am writing this at home and don't remember the details so I will answer this in more detail tomorrow. Damon Register |
|
From: Jogy <jo...@si...> - 2024-09-24 02:10:11
|
Hi, 6.36 and 6.44 are legacy versions that are intended as stepping stones in the upgrade path from OWL 5 7.0 is considered the currently stable production version. The trunk branch is the currently developed version. It used to be 7.1 but then it's version was updated to 8.0 - check this discussion: https://sourceforge.net/p/owlnext/discussion/97177/thread/569a371e2f/ What are the problems you are having with RichEditor? It is best if you post questions in the Open Discussion forum: https://sourceforge.net/p/owlnext/discussion/97175/ Regards, Jogy On 9/22/2024 1:17 PM, Damon Register wrote: > I am struggling to understand all the different versions of OWLNext. > I see on the > OWLNext page > https://sourceforge.net/projects/owlnext/files/source/ > there is 6.36, 6.44, 7.014. > > On https://sourceforge.net/p/owlnext/code/HEAD/tree/ it shows for svn > svn checkout https://svn.code.sf.net/p/owlnext/code/trunk owlnext-code > When I do a svn get I have 8.0.5 > > Two years ago some people in this list were helping me with a > RichEdit problem. > At that time version 7.1 was suggested because it had some > improvements in > the TRichEdit. I have been using 7.1 since then but am having > crashing with > that. Now I don't even remember how I got 7.1 (the svn link). > > Now I am wondering if 7.1 was a development version that was never > released. Is 8.0.5 also a development version? > > I am trying to go back to 7.0.14 but am having trouble with the TRichEdit > control so I found all the e-mail from 2 years ago and have some things > to try tomorrow. > > Damon Register > > > > _______________________________________________ > OWLNext-users mailing list > OWL...@li... > https://lists.sourceforge.net/lists/listinfo/owlnext-users |
|
From: Damon R. <dam...@be...> - 2024-09-22 20:27:58
|
I am struggling to understand all the different versions of OWLNext. I see on the OWLNext page https://sourceforge.net/projects/owlnext/files/source/ there is 6.36, 6.44, 7.014. On https://sourceforge.net/p/owlnext/code/HEAD/tree/ it shows for svn svn checkout https://svn.code.sf.net/p/owlnext/code/trunk owlnext-code When I do a svn get I have 8.0.5 Two years ago some people in this list were helping me with a RichEdit problem. At that time version 7.1 was suggested because it had some improvements in the TRichEdit. I have been using 7.1 since then but am having crashing with that. Now I don't even remember how I got 7.1 (the svn link). Now I am wondering if 7.1 was a development version that was never released. Is 8.0.5 also a development version? I am trying to go back to 7.0.14 but am having trouble with the TRichEdit control so I found all the e-mail from 2 years ago and have some things to try tomorrow. Damon Register |
|
From: Damon R. <dam...@lm...> - 2022-06-23 13:05:03
|
On 6/23/2022 5:13 AM, Vidar Hasfjord wrote: > Thanks for reporting this issue. I'm not familiar with this class, but > post a patch or comment at [feature-requests:#209] "Hide public data > members" for Ognyan to have a look at. I just did. Most of the problems I was able to find the accessor and update my code. The only one I couldn't fix was the one I mentioned in the previous message and this is the one that I posted to [feature-requests:#209] Damon Register |
|
From: Vidar H. <vid...@ou...> - 2022-06-23 09:14:12
|
On 2022-06-22 20:40, Damon Register wrote: > I am looking at THostInfoManager but I don't see how to access HostEntry Thanks for reporting this issue. I'm not familiar with this class, but post a patch or comment at [feature-requests:#209] "Hide public data members" for Ognyan to have a look at. Regards, Vidar |
|
From: Damon R. <dam...@lm...> - 2022-06-22 19:41:20
|
On 4/19/2022 4:47 PM, Vidar Hasfjord wrote:
> The PBS_SMOOTH control style can be used to show a smooth bar instead
> of the default segmented bar. Showing a numerical value is not
> supported, but you can use an accompanying Static control for that.
Having the number inside the control save me a lot of space on my
dialogs.
> Persuade me, you can not. Personally, I want to see the core of
> OWLNext shrink further. Albeit simpler, the advantage with
> TProgressBar is that you
Resistance is futile? :-)
> automatically get the default look and functionality of the native
> Windows UI. That said, TGauge is not gone! It was just moved to
> OWLExt, since it no longer encapsulates a native Windows control. If
> you want it, it is there ("owlext/gauge.h").
Thanks. I found it and have fixed my project to use it.
Today I got the latest 7.1.0 from svn and built it. Now I get a few
compile fails and they
all seem to be related to class members that are now protected. I found
this comment
in defs.h
// Strict data makes all data members private. Accessors must then be used
I believe that I understand what that means but I haven't found the
accessors.
One such item in my code is this
sAddressToSendTo.SetNetworkAddress(myHostInfoManager.HostEntry->GetINetAddress());
HostEntry is now protected so I can't do it this way any more, right?
I am looking at THostInfoManager but I don't see how to access HostEntry or
get the info that GetINetAddress() is returning
Damon Register
|
|
From: Vidar H. <vid...@ou...> - 2022-04-19 20:47:53
|
On 2022-04-19 18:43, Damon Register wrote: > With some really great help from Jogy and Vidar Hasfjord > I have made to great progress in updating my project to MSVC 2022 > and OWLNext 7.1.0. Good! Thanks for the feedback. > Does TProgressBar have the ability to show a continuous bar along with > the > printed value? I checked the OWLNext help for TProgressBar and didn't > find > either of those features. TProgressBar is a thin wrapper around the native Progress Bar control in Windows. For full documentation, see the Windows API documentation. The PBS_SMOOTH control style can be used to show a smooth bar instead of the default segmented bar. Showing a numerical value is not supported, but you can use an accompanying Static control for that. https://docs.microsoft.com/en-us/windows/win32/controls/progress-bar-control-styles > If this can't be done with TProgressBar, could I persuade the > developers to > bring back TGauge? Persuade me, you can not. Personally, I want to see the core of OWLNext shrink further. Albeit simpler, the advantage with TProgressBar is that you automatically get the default look and functionality of the native Windows UI. That said, TGauge is not gone! It was just moved to OWLExt, since it no longer encapsulates a native Windows control. If you want it, it is there ("owlext/gauge.h"). PS. This mailing list has little attendance, so you may be better off using our Discussion forum (it also supports posting and replying using an email client, if you prefer). Regards, Vidar Hasfjord |
|
From: Damon R. <dam...@lm...> - 2022-04-19 17:43:51
|
With some really great help from Jogy and Vidar Hasfjord I have made to great progress in updating my project to MSVC 2022 and OWLNext 7.1.0. My project compiles with MSVC 2022 and OWLNext 7.1.0 and runs so now I am checking for things that don't seem right. I know that TGauge was deprecated so I replaced it with TProgressBar as suggested. I see that I can't use TProgressBar as it is because the bar is segmented and only increments by segment and it doesn't put the value in the middle of the bar. Does TProgressBar have the ability to show a continuous bar along with the printed value? I checked the OWLNext help for TProgressBar and didn't find either of those features. If this can't be done with TProgressBar, could I persuade the developers to bring back TGauge? Damon Register |
|
From: Vidar H. <vid...@ou...> - 2022-03-17 20:13:22
|
On 2022-03-16 16:44, Damon Register wrote: > I had <owl/richedit.h> which resulted in compile errors though it > didn't say > "not found". Why is this? The include file "owl/richedit.h" is a pure C++ file (defines TRichEdit and support classes). It is not designed to be included into a resource script, unlike the Windows API header "richedit.h", which is. The latter has preprocessor directives to disable all the C code and leave only the macro definitions, when included from a resource script. > I don't know what is the difference between [TCharFormat(const > TRichEdit&, ...) and TRichEdit::GetCharFormat] or why [the latter] > method worked but only partially. They should be equivalent, so there are likely other differences in the code. In 7.1, this TCharFormat constructor has been deprecated, so GetCharFormat is the way to go. Regards, Vidar Hasfjord |
|
From: Vidar H. <vid...@ou...> - 2022-03-17 20:10:54
|
On 2022-03-17 17:24, Damon Register wrote: > do you think it is better to eliminate OWL5_COMPAT before or after > upgrading to 6.44? If you keep OWL5_COMPAT enabled, then you postpone the compilation errors you may get when you turn it off. Since there were major changes in 6.44 that may require code rewrite anyhow, it may be easier to keep OWL5_COMPAT enabled, and first deal with the inevitable changes you have to make. On the other hand, you can turn off OWL5_COMPAT in 6.36, modernise your code, upgrade to 6.44, and then — if the number of compilation errors is overwhelming — turn it temporarily on again, while you make the inevitable changes for 6.44. This is a little back-on-forth, but may make the porting process more manageable for you. Regards, Vidar Hasfjord |
|
From: Damon R. <dam...@lm...> - 2022-03-17 17:24:54
|
On 3/4/2022 1:24 AM, Vidar Hasfjord wrote: > https://sourceforge.net/p/owlnext/wiki/Upgrading_from_OWL/#owl-compatibility > > It sounds to me that you still are using Borland C++ in some capacity. I recommend fully migrating > to modern tools and the latest version of OWLNext 6.44/7.0. Then rewrite your code to no longer > rely on OWL5_COMPAT. Now that I am past the richedit problem, I am working on your suggestion and am using the link that you provided. I am up to step 5 in that link's suggested upgrade path. I am using MSVC 2022 and OWLNext 6.36 with OWL5_COMPAT. This compiles and runs with no trouble. I notice a slight difference between the wiki upgrade and what you mentioned in your message. You suggest: 1. upgrade to 6.44/7.0 2. eliminate OWL5_COMPAT while the wiki page suggests: 1. eliminate OWL5_COMPAT 2. upgrade to 6.44/7.0 Is either any better or easier than the other? I tried upgrading to 6.44 while keeping OWL5_COMPAT and got quite a few errors. I see the wiki says that 6.40 had "a major overhaul of the message dispatch machinery" and it looks like the errors are related to that. With this in mind, do you think it is better to eliminate OWL5_COMPAT before or after upgrading to 6.44? Damon Register |
|
From: Damon R. <dam...@lm...> - 2022-03-16 17:50:57
|
On 3/16/2022 12:58 PM, Vidar Hasfjord wrote: > On 2022-03-16 16:44, Damon Register wrote: >> I found that I had the right idea but I misunderstood >> GetFontInfo() and SetFontInfo(). I had them reversed. > > Interesting to hear. I have just recently deprecated these functions on the trunk (version 7.1 in > development) due to the very fact that they were confusing! See [r5853]: I guess that's my life story :-) I start out with something deprecated. > "CHG: Deprecated and relegated the functions GetFontInfo and SetFontInfo to OWL5_COMPAT mode. > These functions are odd and unintuitive, since the former is mutating and the latter is not! The > functions are replaced by functional-style GetFont and SetFont." I just downloaded another svn snapshot. I see there are quite a few changes to the richedit class. I'll have to try the new method. Thanks for the update. Damon Register |
|
From: Vidar H. <vid...@ou...> - 2022-03-16 16:58:37
|
On 2022-03-16 16:44, Damon Register wrote: > I found that I had the right idea but I misunderstood > GetFontInfo() and SetFontInfo(). I had them reversed. Interesting to hear. I have just recently deprecated these functions on the trunk (version 7.1 in development) due to the very fact that they were confusing! See [r5853]: "CHG: Deprecated and relegated the functions GetFontInfo and SetFontInfo to OWL5_COMPAT mode. These functions are odd and unintuitive, since the former is mutating and the latter is not! The functions are replaced by functional-style GetFont and SetFont." Regards, Vidar Hasfjord |
|
From: Damon R. <dam...@lm...> - 2022-03-16 16:44:31
|
On 3/3/2022 3:27 PM, Jogy wrote: > > Hi, > > You can check the "classes" project under the examples folder, in the trunk (7.1) > > I have added to it a TRichEdit in a dialog demo, and it also shows the text background highlighting. > Thanks. My vacation is over so it's back to work. That example was quite helpful finally getting highlighting to work. I did some comparing between my project and your to try to learn the differences. I see two things that might be significant. 1. your resource.rc file has these #include <owl/winres.rh> #include <owl/editfile.rh> #include <owl/mdi.rh> #include <richedit.h> I had <owl/richedit.h> which resulted in compile errors though it didn't say "not found". Why is this? Perhaps the most important difference that I found was the method that you used to obtain the TCharFormat class TCharFormat cf(*richedit); I had richedit->GetCharFormat(cf); I don't know what is the difference between the two or why method worked but only partially. I could use the cf to set the text color (foreground) but the highlighting didn't work. Now that the highlighting is working, I am now trying to change the font size in my hello world example. I found that I had the right idea but I misunderstood GetFontInfo() and SetFontInfo(). I had them reversed. Thanks for all your help with this problem and getting me more up to date. Damon Register |
|
From: Damon R. <dam...@lm...> - 2022-03-16 15:08:23
|
On 3/4/2022 1:24 AM, Vidar Hasfjord wrote: > Hi Damon, > > > I thought that I read somewhere that OWL5 was dropped after 6.36. > > I guess you read, in our wiki article "Upgrading from OWL", that Borland C++, the compiler, is not > supported beyond the 6.30 series. However, the OWLNext API is still pretty much compatible with > OWL 5 and still supports the OWL5_COMPAT build mode for even greater compatibility. That was probably what I read. I gave up keeping compatibility with Borland 5 because it had its own quirks. The only thing I use it for is editing my dialogs. > It sounds to me that you still are using Borland C++ in some capacity. I recommend fully migrating > to modern tools and the latest version of OWLNext 6.44/7.0. Then rewrite your code to no longer > rely on OWL5_COMPAT. I think that is what I am going to do. I found out that the free version of MSVC 2022 is enough to build my project so I now have MSVC 2022 and OWLNext 7 to work with. I will take a look at that link that you provided to try to update my project. Damon Register |
|
From: Vidar H. <vid...@ou...> - 2022-03-04 06:24:54
|
Hi Damon, > I thought that I read somewhere that OWL5 was dropped after 6.36. I guess you read, in our wiki article "Upgrading from OWL", that Borland C++, the compiler, is not supported beyond the 6.30 series. However, the OWLNext API is still pretty much compatible with OWL 5 and still supports the OWL5_COMPAT build mode for even greater compatibility. https://sourceforge.net/p/owlnext/wiki/Upgrading_from_OWL/#owl-compatibility It sounds to me that you still are using Borland C++ in some capacity. I recommend fully migrating to modern tools and the latest version of OWLNext 6.44/7.0. Then rewrite your code to no longer rely on OWL5_COMPAT. Regards, Vidar Hasfjord |
|
From: Damon R. <dam...@lm...> - 2022-03-03 21:09:36
|
On 3/3/2022 3:27 PM, Jogy wrote: > > Hi, > > You can check the "classes" project under the examples folder, in the trunk (7.1) > > I have added to it a TRichEdit in a dialog demo, and it also shows the text background highlighting. > Thanks. I will certainly build that one. Damon Register |
|
From: Jogy <jo...@si...> - 2022-03-03 20:27:37
|
Hi, You can check the "classes" project under the examples folder, in the trunk (7.1) I have added to it a TRichEdit in a dialog demo, and it also shows the text background highlighting. Jogy On 3/3/2022 9:58 AM, Damon Register wrote: > On 3/2/2022 7:17 PM, Jogy wrote: >> OWLNext 6.44 also has OWL5 compatibility in case you need it. >> >> Even 7.x has it. > That is strange. I thought that I read somewhere that OWL5 was dropped > after 6.36. If course I can't remember where I saw that. > > >> "RichEdit" is the old control class, for RichEdit 1.0, that is why it >> does not work - so definitely the app is defaulting to RichEdit 2.0 >> or newer. > that certainly explains the problem there. Thanks > >> You can use the RICHEDIT_CLASS define: >> CONTROL "richtest", IDC_RICHEDIT, RICHEDIT_CLASS, ES_MULTILINE | >> ES_AUTOVSCROLL | ES_AUTOHSCROLL | WS_CHILD | WS_VISIBLE | WS_BORDER | >> WS_VSCROLL | WS_HSCROLL, 10, 10, 280, 180 >> >> to access it, you need to include richedit.h in the rc file. > I tried this and the compile fails. I found that just including > richedit.h in the rc file > causes the compile fail. > 1>D:\owlnext-6.44_svn_13\include\owl/private/defs.h(14): error RC2188: > D:\owlnext-6.44_svn_13\include\owl/private/defs.h(139) : error RC2188: > C:\Program Files (x86)\Microsoft Visual Studio > 12.0\VC\include\memory.h(52) : warning RC4011: identifier truncated to > '_CRT_SECURE_CPP_OVERLOAD_STANDA' > > >> Wonder if the presence of CFM_COLOR in the mask causes issue. >> >> You can check the return value of SetCharFormat, and if it is false, >> call GetLastError to see why the Win32API call has failed. > It returned true > >> I made the fix in OWLNext source, and now the background text sets >> properly. >> >> You can try to checkout latest OWLNext 6.44 from SourceForge SVN >> repository and build it. > I am a little rusty with SVN but I figured it out. I downloaded it > and noticed your > comments about this issue. > > I got MSVC 2022 and built a 2013 and 2022 version of 6.44 from svn. > I tried my hello world project in both 2013 and 2022. The problems remain > the same. The text will not highlight and adding richedit.h to the rc > causes > the compile errors. > > So, at this point I am still stuck. I can't get highlighting to > work. After a little more > Google today, I am wondering if I am thinking of something different > than you are, > but I am not certain. In this case background color refers to only a > portion of the > text, right? > > > I downloaded 7.1.0 from svn too and built it with MSVC 2022. I will > try that to see > if the result is any different. > > Damon Register > > > > _______________________________________________ > OWLNext-users mailing list > OWL...@li... > https://lists.sourceforge.net/lists/listinfo/owlnext-users |
|
From: Damon R. <dam...@lm...> - 2022-03-03 19:19:30
|
On 3/2/2022 7:17 PM, Jogy wrote: > OWLNext 6.44 also has OWL5 compatibility in case you need it. > > Even 7.x has it. That is strange. I thought that I read somewhere that OWL5 was dropped after 6.36. If course I can't remember where I saw that. > "RichEdit" is the old control class, for RichEdit 1.0, that is why it does not work - so > definitely the app is defaulting to RichEdit 2.0 or newer. that certainly explains the problem there. Thanks > You can use the RICHEDIT_CLASS define: > CONTROL "richtest", IDC_RICHEDIT, RICHEDIT_CLASS, ES_MULTILINE | ES_AUTOVSCROLL | ES_AUTOHSCROLL | > WS_CHILD | WS_VISIBLE | WS_BORDER | WS_VSCROLL | WS_HSCROLL, 10, 10, 280, 180 > > to access it, you need to include richedit.h in the rc file. I tried this and the compile fails. I found that just including richedit.h in the rc file causes the compile fail. 1>D:\owlnext-6.44_svn_13\include\owl/private/defs.h(14): error RC2188: D:\owlnext-6.44_svn_13\include\owl/private/defs.h(139) : error RC2188: C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\include\memory.h(52) : warning RC4011: identifier truncated to '_CRT_SECURE_CPP_OVERLOAD_STANDA' > Wonder if the presence of CFM_COLOR in the mask causes issue. > > You can check the return value of SetCharFormat, and if it is false, call GetLastError to see why > the Win32API call has failed. It returned true > I made the fix in OWLNext source, and now the background text sets properly. > > You can try to checkout latest OWLNext 6.44 from SourceForge SVN repository and build it. I am a little rusty with SVN but I figured it out. I downloaded it and noticed your comments about this issue. I got MSVC 2022 and built a 2013 and 2022 version of 6.44 from svn. I tried my hello world project in both 2013 and 2022. The problems remain the same. The text will not highlight and adding richedit.h to the rc causes the compile errors. So, at this point I am still stuck. I can't get highlighting to work. After a little more Google today, I am wondering if I am thinking of something different than you are, but I am not certain. In this case background color refers to only a portion of the text, right? I downloaded 7.1.0 from svn too and built it with MSVC 2022. I will try that to see if the result is any different. Damon Register |
|
From: Jogy <jo...@si...> - 2022-03-03 00:18:06
|
>> OWLNext 6.36 is quite old, and receives only limited support. > The main reason I am stuck on 6.36 is that it is the last to support > OWL5 compatibility > OWLNext 6.44 also has OWL5 compatibility in case you need it. Even 7.x has it. >> I recommend to use at least OWLNext 6.4.4. > I tried OWLNext 7 but I found out quickly that it doesn't support > MSVC 2013. > > I have downloaded and built OWLNext 6.4.4. I removed the OWL5_COMPAT > from my hello world app. > >> The first constructor should work when you are putting the rich edit >> as a control in a dialog. >> >> I haven't done so before, but I will give it a try. > Since I am now using 6.4.4 as you suggested, I tried the first > constructor > again. I still get this error: > a dialog box with Unhandled exception Create fail for window "", ID: > 0, window class TMyDlg > I am still using Borland 5.02 for dialog box editing. Perhaps > something is > missing in the way I setup the control? from the RC file: > CONTROL "richtest", IDC_EDIT_EVENTS, "RichEdit", ES_MULTILINE | > ES_AUTOVSCROLL | ES_AUTOHSCROLL | WS_CHILD | WS_VISIBLE | WS_BORDER | > WS_VSCROLL | WS_HSCROLL, 10, 30, 574, 322 > or worse, the Borland 5.02 creates something that can't work with > this? > "RichEdit" is the old control class, for RichEdit 1.0, that is why it does not work - so definitely the app is defaulting to RichEdit 2.0 or newer. You can use the RICHEDIT_CLASS define: CONTROL "richtest", IDC_RICHEDIT, RICHEDIT_CLASS, ES_MULTILINE | ES_AUTOVSCROLL | ES_AUTOHSCROLL | WS_CHILD | WS_VISIBLE | WS_BORDER | WS_VSCROLL | WS_HSCROLL, 10, 10, 280, 180 to access it, you need to include richedit.h in the rc file. > >> There is a class TRichEditModule, and instantiating it and calling >> it's member function GetVersion() should return which version is >> being used. > I just did that and it returned 2 > >> In OWLNext 6.44 and onward there is a RichEditor example that >> includes a TRichEdit control. > I will take a look at that. > > from your later two messages: > cf.SetBkColor(*tColorGreen); > cf.dwMask |= CFM_BACKCOLOR; > cf.dwEffects &= ~CFE_AUTOBACKCOLOR; > idc_edit_events->SetCharFormat(cf); > > Sadly I still don't have highlighted text > > Wonder if the presence of CFM_COLOR in the mask causes issue. You can check the return value of SetCharFormat, and if it is false, call GetLastError to see why the Win32API call has failed. I made the fix in OWLNext source, and now the background text sets properly. You can try to checkout latest OWLNext 6.44 from SourceForge SVN repository and build it. Jogy |
|
From: Damon R. <dam...@lm...> - 2022-03-02 19:23:16
|
On 3/2/2022 11:43 AM, Jogy wrote: > > Hello, > > there is more activity on the discussion forum: > > https://sourceforge.net/p/owlnext/discussion/97175/ Thanks for taking the time to reply to my questions > What compiler are you targeting to use with OWLNext? Visual Studio 2013 > OWLNext 6.36 is quite old, and receives only limited support. The main reason I am stuck on 6.36 is that it is the last to support OWL5 compatibility > I recommend to use at least OWLNext 6.4.4. I tried OWLNext 7 but I found out quickly that it doesn't support MSVC 2013. I have downloaded and built OWLNext 6.4.4. I removed the OWL5_COMPAT from my hello world app. > The first constructor should work when you are putting the rich edit as a control in a dialog. > > I haven't done so before, but I will give it a try. Since I am now using 6.4.4 as you suggested, I tried the first constructor again. I still get this error: a dialog box with Unhandled exception Create fail for window "", ID: 0, window class TMyDlg I am still using Borland 5.02 for dialog box editing. Perhaps something is missing in the way I setup the control? from the RC file: CONTROL "richtest", IDC_EDIT_EVENTS, "RichEdit", ES_MULTILINE | ES_AUTOVSCROLL | ES_AUTOHSCROLL | WS_CHILD | WS_VISIBLE | WS_BORDER | WS_VSCROLL | WS_HSCROLL, 10, 30, 574, 322 or worse, the Borland 5.02 creates something that can't work with this? > There is a class TRichEditModule, and instantiating it and calling it's member function > GetVersion() should return which version is being used. I just did that and it returned 2 > In OWLNext 6.44 and onward there is a RichEditor example that includes a TRichEdit control. I will take a look at that. from your later two messages: cf.SetBkColor(*tColorGreen); cf.dwMask |= CFM_BACKCOLOR; cf.dwEffects &= ~CFE_AUTOBACKCOLOR; idc_edit_events->SetCharFormat(cf); Sadly I still don't have highlighted text Damon Register |
|
From: Jogy <jo...@si...> - 2022-03-02 18:00:24
|
Update: fixing the flag is not enough, you also need to clear the CFE_AUTOBACKCOLOR flag from dwEffects: cf.dwEffects &= ~CFE_AUTOBACKCOLOR; Jogy On 3/2/2022 9:29 AM, Jogy wrote: > Hi, > > > after digging a bit, there seems to be a bug: > The implementation of TCharFormat::SetBkColor sets the wrong mask bit > - CFM_COLOR instead of CFM_BACKCOLOR. > > I will fix this bug for future releases, but in the meantime, you can > try to manually add it: > cf.SetBkColor(*tColorGreen); > > cf.dwMask |= CFM_BACKCOLOR; > > idc_edit_events->SetCharFormat(cf); > > > Thanks for uncovering this issue. > > Jogy > > > On 3/2/2022 8:43 AM, Jogy wrote: >> >> Hello, >> >> On 3/2/2022 4:36 AM, Damon Register wrote: >>> I haven't seen much activity in this list. I hope it is still alive. >>> I am really struggling to understand and use the richedit control. >> >> there is more activity on the discussion forum: >> >> https://sourceforge.net/p/owlnext/discussion/97175/ >> >> Everyone can post there, although it is best if you have a >> SourceForge account and post with it. >> >> I have created a simple hello world app with one richedit control. >>> I am using owlnext 6.36 with OWL5_COMPAT. Certainly my >>> hello world app doesn't need OWL5_COMPAT but the app that I >>> am trying to add a richedit control does. >>> >> What compiler are you targeting to use with OWLNext? >> >> OWLNext 6.36 is quite old, and receives only limited support. >> >> I recommend to use at least OWLNext 6.4.4. >> >> >>> I never could get it to work with a richedit control in the resource >>> editor and constructor >>> idc_edit_events = new owl::TRichEdit(this, IDC_EDIT_EVENTS); >>> but I was able to use >>> idc_edit_events = new owl::TRichEdit(this, IDC_EDIT_EVENTS, "init >>> text", 10, 40, 900, 560); >>> so I can live with that. >>> >> The first constructor should work when you are putting the rich edit >> as a control in a dialog. >> >> I haven't done so before, but I will give it a try. >> >> >>> Part of the confusion that I have is whether Owlnext 6.36 is using >>> richedit 1.0 or 2.0. Somewhere I thought I read that it might be 1.0. >>> Which one is being used? Is there a choice? >>> >> There is some logic to choose based on availability, but I guess that >> on all currently supported versions of Windows it will be the newest >> one (2.0, or even 4.1) >> >> There is a class TRichEditModule, and instantiating it and calling >> it's member function GetVersion() should return which version is >> being used. >> >> >>> In my hello world app I can do most of the things that I want to do >>> with a richedit control, insert some text, paste some text, and change >>> the color of some text. There is one thing that I cannot do yet (and >>> I need it) is text highlighting (changing the background color of some >>> text). >>> >>> I can change text color with >>> cf.SetTextColor(*tColorRed); >>> idc_edit_events->SetCharFormat(cf); >>> Would this be the normal way of changing some text color? >>> >>> To change the highlighting I tried this >>> cf.SetBkColor(*tColorGreen); >>> idc_edit_events->SetCharFormat(cf); >>> but this has no effect. >>> >>> What is really strange is that I can cut a section of text from >>> another document that includes some highlighted text and paste this >>> into my richedit and the highlighting is there. >>> >>> Is there anyone who can help me with this? >>> >> In OWLNext 6.44 and onward there is a RichEditor example that >> includes a TRichEdit control. >> >> Currently it has the ability only to change the text color, but I >> will see how to implement background color change as well. >> >> Jogy >> >> >> >>> Damon Register >>> >>> >>> >>> >>> _______________________________________________ >>> OWLNext-users mailing list >>> OWL...@li... >>> https://lists.sourceforge.net/lists/listinfo/owlnext-users >> >> >> _______________________________________________ >> OWLNext-users mailing list >> OWL...@li... >> https://lists.sourceforge.net/lists/listinfo/owlnext-users > > > _______________________________________________ > OWLNext-users mailing list > OWL...@li... > https://lists.sourceforge.net/lists/listinfo/owlnext-users |
|
From: Jogy <jo...@si...> - 2022-03-02 17:29:27
|
Hi, after digging a bit, there seems to be a bug: The implementation of TCharFormat::SetBkColor sets the wrong mask bit - CFM_COLOR instead of CFM_BACKCOLOR. I will fix this bug for future releases, but in the meantime, you can try to manually add it: cf.SetBkColor(*tColorGreen); cf.dwMask |= CFM_BACKCOLOR; idc_edit_events->SetCharFormat(cf); Thanks for uncovering this issue. Jogy On 3/2/2022 8:43 AM, Jogy wrote: > > Hello, > > On 3/2/2022 4:36 AM, Damon Register wrote: >> I haven't seen much activity in this list. I hope it is still alive. >> I am really struggling to understand and use the richedit control. > > there is more activity on the discussion forum: > > https://sourceforge.net/p/owlnext/discussion/97175/ > > Everyone can post there, although it is best if you have a SourceForge > account and post with it. > > I have created a simple hello world app with one richedit control. >> I am using owlnext 6.36 with OWL5_COMPAT. Certainly my >> hello world app doesn't need OWL5_COMPAT but the app that I >> am trying to add a richedit control does. >> > What compiler are you targeting to use with OWLNext? > > OWLNext 6.36 is quite old, and receives only limited support. > > I recommend to use at least OWLNext 6.4.4. > > >> I never could get it to work with a richedit control in the resource >> editor and constructor >> idc_edit_events = new owl::TRichEdit(this, IDC_EDIT_EVENTS); >> but I was able to use >> idc_edit_events = new owl::TRichEdit(this, IDC_EDIT_EVENTS, "init >> text", 10, 40, 900, 560); >> so I can live with that. >> > The first constructor should work when you are putting the rich edit > as a control in a dialog. > > I haven't done so before, but I will give it a try. > > >> Part of the confusion that I have is whether Owlnext 6.36 is using >> richedit 1.0 or 2.0. Somewhere I thought I read that it might be 1.0. >> Which one is being used? Is there a choice? >> > There is some logic to choose based on availability, but I guess that > on all currently supported versions of Windows it will be the newest > one (2.0, or even 4.1) > > There is a class TRichEditModule, and instantiating it and calling > it's member function GetVersion() should return which version is being > used. > > >> In my hello world app I can do most of the things that I want to do >> with a richedit control, insert some text, paste some text, and change >> the color of some text. There is one thing that I cannot do yet (and >> I need it) is text highlighting (changing the background color of some >> text). >> >> I can change text color with >> cf.SetTextColor(*tColorRed); >> idc_edit_events->SetCharFormat(cf); >> Would this be the normal way of changing some text color? >> >> To change the highlighting I tried this >> cf.SetBkColor(*tColorGreen); >> idc_edit_events->SetCharFormat(cf); >> but this has no effect. >> >> What is really strange is that I can cut a section of text from >> another document that includes some highlighted text and paste this >> into my richedit and the highlighting is there. >> >> Is there anyone who can help me with this? >> > In OWLNext 6.44 and onward there is a RichEditor example that includes > a TRichEdit control. > > Currently it has the ability only to change the text color, but I will > see how to implement background color change as well. > > Jogy > > > >> Damon Register >> >> >> >> >> _______________________________________________ >> OWLNext-users mailing list >> OWL...@li... >> https://lists.sourceforge.net/lists/listinfo/owlnext-users > > > _______________________________________________ > OWLNext-users mailing list > OWL...@li... > https://lists.sourceforge.net/lists/listinfo/owlnext-users |
|
From: Jogy <jo...@si...> - 2022-03-02 17:22:15
|
Hello, On 3/2/2022 4:36 AM, Damon Register wrote: > I haven't seen much activity in this list. I hope it is still alive. > I am really struggling to understand and use the richedit control. there is more activity on the discussion forum: https://sourceforge.net/p/owlnext/discussion/97175/ Everyone can post there, although it is best if you have a SourceForge account and post with it. I have created a simple hello world app with one richedit control. > I am using owlnext 6.36 with OWL5_COMPAT. Certainly my > hello world app doesn't need OWL5_COMPAT but the app that I > am trying to add a richedit control does. > What compiler are you targeting to use with OWLNext? OWLNext 6.36 is quite old, and receives only limited support. I recommend to use at least OWLNext 6.4.4. > I never could get it to work with a richedit control in the resource > editor and constructor > idc_edit_events = new owl::TRichEdit(this, IDC_EDIT_EVENTS); > but I was able to use > idc_edit_events = new owl::TRichEdit(this, IDC_EDIT_EVENTS, "init > text", 10, 40, 900, 560); > so I can live with that. > The first constructor should work when you are putting the rich edit as a control in a dialog. I haven't done so before, but I will give it a try. > Part of the confusion that I have is whether Owlnext 6.36 is using > richedit 1.0 or 2.0. Somewhere I thought I read that it might be 1.0. > Which one is being used? Is there a choice? > There is some logic to choose based on availability, but I guess that on all currently supported versions of Windows it will be the newest one (2.0, or even 4.1) There is a class TRichEditModule, and instantiating it and calling it's member function GetVersion() should return which version is being used. > In my hello world app I can do most of the things that I want to do > with a richedit control, insert some text, paste some text, and change > the color of some text. There is one thing that I cannot do yet (and > I need it) is text highlighting (changing the background color of some > text). > > I can change text color with > cf.SetTextColor(*tColorRed); > idc_edit_events->SetCharFormat(cf); > Would this be the normal way of changing some text color? > > To change the highlighting I tried this > cf.SetBkColor(*tColorGreen); > idc_edit_events->SetCharFormat(cf); > but this has no effect. > > What is really strange is that I can cut a section of text from > another document that includes some highlighted text and paste this > into my richedit and the highlighting is there. > > Is there anyone who can help me with this? > In OWLNext 6.44 and onward there is a RichEditor example that includes a TRichEdit control. Currently it has the ability only to change the text color, but I will see how to implement background color change as well. Jogy > Damon Register > > > > > _______________________________________________ > OWLNext-users mailing list > OWL...@li... > https://lists.sourceforge.net/lists/listinfo/owlnext-users |