IonicWind Software

Aurora Compiler => Software Projects => Topic started by: Bruce Peaslee on March 17, 2006, 03:07:58 PM

Title: Hood Map
Post by: Bruce Peaslee on March 17, 2006, 03:07:58 PM
Here is something I designed for my own use. It is hardly commercial quality, but it does show:


---

Edit: I added the necessary include files to the ZIP.
Title: Re: Hood Map
Post by: Doc on March 17, 2006, 05:51:01 PM
Hey Bruce,

With me being a die -n- the wool (completely dedicated) "browser head", I have to say that this is by far the most interesting, if not unique use of an embedded browser that I've seen to date. Why didn't I think of that!  ::)

...well obviously I didn't, but you sure gave me a great idea anyway.  ;D

Thanks!

-Doc-
Title: Re: Hood Map
Post by: Haim on March 17, 2006, 09:11:24 PM
Could not build HoodMap.
Where do I find all those .inc files? (I have only the webbrowser.inc file) Can they be downloaded from somewhere?
Also instructions on building the project would be a great  help for me as I have worked with single file programs only.
Title: Re: Hood Map
Post by: Ionic Wind Support Team on March 17, 2006, 09:13:54 PM
The CWebBrowser class is posted in the Software projects forum, a few topics lower than this one ;)

That is where you get it.   Of course searching for it would have gotten you there too.
Title: Re: Hood Map
Post by: Haim on March 17, 2006, 09:29:33 PM
Thanks,
As I said,I did not miss the webbrowser.inc file but the other inc's in the HoodMap project (API.inc, AdditionalConstants.inc)
Search did not find them...
Title: Re: Hood Map
Post by: Bruce Peaslee on March 17, 2006, 10:32:01 PM
Sorry, I missed that. I usually replace the include directive with the actual code, but I forgotÂÃ,  :P

Here are the relevant includes.

_______________________

Edit: these files are now part of the ZIP file in the first post.
Title: Re: Hood Map
Post by: Bruce Peaslee on April 02, 2006, 09:12:34 PM
The scrolling was always jumpy and trying to compute what portion of the screen should be repainted was a nightmare. So I decided instead on the following: the painting is done on a bitmap that is stored in memory. Whatever portion of the screen should be seen at any one time - either the original screen, a resized screen, or a scrolled screen - is block transfered from the bitmap as needed. It is fast enough to smooth out the scrolling nicely.

It was a lot of work to figure all of this out. I may design a window class for the future.