> as I have a few other things I want to implement I might not get to > them. Anyway, that branch is available at: > > https://github.com/evanbattaglia/viking/tree/imageboxlayer > > A sample compass rose is in doc/sample-compassrose.png. > Let me know if any of you have questions about this feature. >
After some initial doubts about this I now see how this feature could be useful to me. I've replied separately to Evan with some thoughts on user visible issues. Make it clearer it's an Output thing so I dubbed it Image Output Box. (IOB) So I hope we can integrate this for future Viking 1.4. Points I want to get correct are especially getting the .vik file name internal variable names 'correct' - as we're kind of tied into 'supporting' that text format, which can making future changes hard to be backwards compatible - if that is a long term principal worth maintaining. Such that having a compass rose overlay is not *only* a compass rose, it could be anything - so naming is important. Rework the actual image code generation into separate image_output_box.c file so that it provides common functions for the Layer and existing Generate Image functionality in vikwindow.c Further ideas are having multiple boxes: Group in Aggregate layers (no new code needed as opposed to multiple boxes in an IOB layer) When an IOB layer is selected - some form of highlight would be good - e.g. make the box have the highlight around the box. (new code) >From the Aggregate layer have a 'Run Generation' which runs the map generation >for each IOB visible. > Just FYI, some of the features I would like to implement that I believe > are not in Viking, and may or may be working on depending on time: > * labeling a track with its length, probably in the middle, and > showing the endpoints more prominently. Again, this is to generate map > similar to http://www.phlumf.com/travels/cdt/cdtmaps.shtml (see > sample http://www.phlumf.com/travels/cdt/mt62.gif) We could have an option to generate a waypoint which is then named 'Track Name', positioned at the middle. Then it's easy to : a - code it b - use it - as the user can see it / move it / hide it / whatever ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ Viking-devel mailing list Viking-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viking-devel Viking home page: http://viking.sf.net/
