From: Jogy on 18 Jan 2010 04:17 "Hector Santos" wrote: > Jogy, > > I'm been trying to download the OwlNext source code from > > http://cc.embarcadero.com/item/27219 > > There is no server response and I tried from SOHO and from my company > network - two different sub-nets. What gives with this company that > took over the once upon a time 'best kept secret' in the market? :) > Try again, it is possible that theirs servers were down during the weekend. > Also, is there a minimum patch available to resolve the thunking issue > within a BC 4.5 compile? > Well, no. OWLNext was based on OWL5.0 which came with Borland C++ 5.01/5.02 and was the last official OWL version. You will have to port to OWLNext, which at the beginning can be not an easy task. But if you want to maintain and update your applications to work under the new versions of Windows, this is the way to go. Jogy > Thanks > > -- > HLS > > Hector Santos wrote: > > > Hi Jogy, > > > > I really did try to search for a "group" that took over OWL. It was hard > > to believe that this issue was not already encountered and addressed in > > some OWL patch or 3rd party update. I am normally a good researcher but > > I missed this one. :) > > > > So I appreciate your input and I will most definitely look into > > OwlNext. I will be interested to see how much single sourcing I can do > > by compiling with the VS C/C++ compiler. :) > > > > Thanks for the input again. > > > . >
From: Hector Santos on 18 Jan 2010 05:33 Hi. I was able to finally download it. Yes, a major change, just looking at OWL.CPP It might be easier to do a pure port to MFC. :) Thanks again. Jogy wrote: > > "Hector Santos" wrote: > >> Jogy, >> >> I'm been trying to download the OwlNext source code from >> >> http://cc.embarcadero.com/item/27219 >> >> There is no server response and I tried from SOHO and from my company >> network - two different sub-nets. What gives with this company that >> took over the once upon a time 'best kept secret' in the market? :) >> > > Try again, it is possible that theirs servers were down during the weekend. > > >> Also, is there a minimum patch available to resolve the thunking issue >> within a BC 4.5 compile? >> > > Well, no. OWLNext was based on OWL5.0 which came with Borland C++ 5.01/5.02 > and was the last official OWL version. > > You will have to port to OWLNext, which at the beginning can be not an easy > task. > > But if you want to maintain and update your applications to work under the > new versions of Windows, this is the way to go. > > Jogy > > > > > >> Thanks >> >> -- >> HLS >> >> Hector Santos wrote: >> >>> Hi Jogy, >>> >>> I really did try to search for a "group" that took over OWL. It was hard >>> to believe that this issue was not already encountered and addressed in >>> some OWL patch or 3rd party update. I am normally a good researcher but >>> I missed this one. :) >>> >>> So I appreciate your input and I will most definitely look into >>> OwlNext. I will be interested to see how much single sourcing I can do >>> by compiling with the VS C/C++ compiler. :) >>> >>> Thanks for the input again. >>> >> . >> -- HLS
From: Jogy on 18 Jan 2010 07:06 "Hector Santos" wrote: > Hi. I was able to finally download it. Yes, a major change, just > looking at OWL.CPP It might be easier to do a pure port to MFC. :) > > Thanks again. > Hello, I doubt that a pure port to MFC will be easier, it would need a complete rewrite of the UI :-) In this case, it is better to move to a more modern framework, like WinForms.NET But the changes from OWL 2 to OWLNext are not that big, the core of the framework is still the same. Check this article: http://owlnext.sourceforge.net/articleowlcompat.html It shows most of the changes in the methods of OWL2 classes and how to replace them. Jogy
First
|
Prev
|
Pages: 1 2 Prev: WM_TIMECHANGE Message Event Next: SetWindowLong GWL_WNDPROC XP,2003 - SOLVED |