Aha! As usual, something I never would have thought of-culprit was indeed the inherited logging level. Thanks for the quick help!
Daniel
-----Original Message-----
From: Don Dietrick [mailto:dfdietrick_at_gmail.com]
Sent: Wednesday, June 27, 2012 11:14 AM
To: Coltey, Daniel
Cc: openmap-users_at_bbn.com
Subject: Re: [OpenMap Users] Border around OMRaster object
Hi Daniel,
I'm glad to hear that the upgrade to OM5 went smoothly.
I'd check to see if the OMRasters are 'selected', too. Looking at the OMRasterObject code, that rectangle gets rendered if the OMRaster has the selected flag set or if the com.bbn.openmap.omGraphics.OMRasterObject logging level is set to FINER.
Hope this helps,
Don
On Jun 27, 2012, at 11:59 AM, Coltey, Daniel wrote:
> Hello all- I've been tasked with maintenance on a system we have that was previously using an artifact tagged OpenMapv1.0.0. I upgraded to the available 5.0.0 package [which went unexpectedly smoothly, btw] but have an annoying issue that has popped up. Our application applies many layers to the map, most of which have OMRaster images on them. With this new version, all of these images have rectangular boxes/borders around them. The only thing I have thought to check using the archives as a reference is the isMatted tag, but that seems to always come back false.
>
> I have attempted to isolate anything that we may be doing; the only thing being displayed currently for test purposes is a single OMRaster object on a single layer. When the map is instantiated outside of our app, there are no borders. Any ideas as to where I should be looking/what I should be looking for that could be causing this? Thanks.
>
> Daniel Coltey
>
--
[To unsubscribe to this list send an email to "majdart_at_bbn.com"
with the following text in the BODY of the message "unsubscribe openmap-users"]
Received on Wed Jun 27 2012 - 13:38:12 EDT