MapTools.org

[Chameleon] map image not placed correctly

bartvde@xs4all.nl bartvde@xs4all.nl
Fri, 9 Jan 2004 11:29:09 +0100 (CET)
Hi Paul,

you're right about that, didn't think about this one ...

But then two optional CWC2 attributes which would determine the absolute
positioning (x,y) would solve my issues ...

Or more simple, I will position the map with an extra div element around
the map widget in my HTML template. I tried this and it will solve my
issues.

Thanks for the idea.

Best regards,
Bart

Hi Paul,

you're right about that, didn't think about this one ...

But then two optional CWC2 attributes which would determine the absolute
positioning (x,y) would solve my issues ...

Or more simple, I will position the map with an extra div element around
the map widget in my HTML template. I tried this and it will solve my
issues.

Thanks for the idea.

Best regards,
Bart

> Although if you look at the source of their page, they use an absolutely
> positioned div.  Remember that we are attempting to provide a placeable
> map image anywhere on the page for any given template, regardless of the
> HTML that the user uses around the widget.  This is somewhat more
> complex than having a single application.
>
> Cheers,
>
> Paul
>
> Bart van den Eijnden wrote:
>
>> Hi Paul,
>>
>> if you look at Intergraph's WMS viewer
>> (http://www.wmsviewer.com/main.asp) you can see they do not have the
>> problem.
>>
>> Although because they do not have a marquee and they have a white
>> background the problem would be less evident in their case, and less
>> easy to notice.
>>
>> So there must be some kind of solution, likely easier than the new
>> solution you are suggesting.
>>
>> Best regards,
>> Bart
>>
>> On Thu, 08 Jan 2004 17:00:52 -0500, Paul Spencer <pagameba@magma.ca>
>> wrote:
>>
>>> Bart,
>>>
>>> I think it is a similar problem in all browsers but due to the
>>> differences in how the pages are laid out by the browser (i.e. the
>>> order that things happen) it is not always apparent.  IE seems to be
>>> the worst because it is the most accomodating and will allow the page
>>> to finish loading without knowing the sizes of images because it can
>>> move things around after the page has loaded.
>>>
>>> I am actually thinking of a new solution to this that would embed the
>>> image in the page rather than on a layer.  The only reason to have it
>>> on a layer right now is to support the dynamic drag pan of the image.
>>> I think that the drag pan widget can create it's own layer and
>>> position it at the right position with a copy of the map image at the
>>> time the tool is selected.  The only downside to this is that the map
>>> image is not currently stored on disk ... and I don't want to trigger
>>> two draws of the map image if I can help it.
>>>
>>> Anyway, food for thought.
>>>
>>> Cheers,
>>>
>>> Paul
>>>
>>> Bart van den Eijnden wrote:
>>>
>>>> Hi Paul, JF,
>>>>
>>>> I am not totally convinced this is solely an IE bug.
>>>>
>>>> I have also seen this happen in Opera.
>>>>
>>>> Also, when putting Mozilla Firebird in fullscreen mode (F11), the
>>>> same thing happens.
>>>>
>>>> Is there already a bugzilla entry for this?
>>>>
>>>> Best regards,
>>>> Bart
>>>>
>>>> On Thu, 08 Jan 2004 13:00:04 -0500, Paul Spencer <pagameba@magma.ca>
>>>> wrote:
>>>>
>>>>> Bart
>>>>>
>>>>> JF has summed it up correctly AFAIK.  I don't think there is a quick
>>>>> fix, but you can check the source of your page for IMG tags that
>>>>> don't have a width/height and if those are coming from widgets then
>>>>> let me know and I will try to fix them asap for you.  But I don't
>>>>> know if this will actually correct the problem entirely.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Paul
>>>
>>>
>>>>> Jean-Francois.Doyon@ccrs.nrcan.gc.ca wrote:
>>>>>
>>>>>> Bart,
>>>>>>
>>>>>> That's an IE bug related to it's rendering engine. The basic
>>>>>> problem is that
>>>>>> IE sometimes positions things before having all necessary
>>>>>> information ... So
>>>>>> it trips over itself and renders elements in the wrong place,
>>>>>> because it
>>>>>> renders/places it TOO early.
>>>>>>
>>>>>> We too have noticed it and will hopefully be working with DM to get
>>>>>> this
>>>>>> fixed.  I've run into this same bug in different circumstances
>>>>>> myself, where
>>>>>> images inside tables that don't have a width/height specified in
>>>>>> the IMG
>>>>>> element sometimes get badly positioned.
>>>>>>
>>>>>> In this case the problem is slightly more complicated I believe,
>>>>>> Paul can
>>>>>> explain further :)
>>>>>>
>>>>>> J.F.
>>>>>>
>>>>>> -----Original Message-----
>>>>>> From: chameleon-admin@lists.maptools.org
>>>>>> [mailto:chameleon-admin@lists.maptools.org]On Behalf Of
>>>>>> bartvde@xs4all.nl
>>>>>> Sent: Thursday, January 08, 2004 11:53 AM
>>>>>> To: chameleon@lists.maptools.org
>>>>>> Subject: [Chameleon] map image not placed correctly
>>>>>>
>>>>>>
>>>>>> Hi list,
>>>>>>
>>>>>> does anybody know what is causing the map image to be displaced the
>>>>>> first
>>>>>> time a Chameleon page is loaded?
>>>>>>
>>>>>> The border is placed correctly, but the map image is mostly around
>>>>>> 50
>>>>>> pixels down from the border and a bit to the right.
>>>>>>
>>>>>> After a zoom action, this corrects itself.
>>>>>>
>>>>>> Any quick and dirty solution for this?
>>>>>>
>>>>>> Best regards,
>>>>>> Bart
>>>>>> _______________________________________________
>>>>>> Chameleon mailing list
>>>>>> Chameleon@lists.maptools.org
>>>>>> http://lists.maptools.org/mailman/listinfo/chameleon
>>>>>> _______________________________________________
>>>>>> Chameleon mailing list
>>>>>> Chameleon@lists.maptools.org
>>>>>> http://lists.maptools.org/mailman/listinfo/chameleon
>>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>
>>
>>
>
> --
>   -----------------------------------------------------------------
> |Paul Spencer                           spencer@dmsolutions.ca    |
> |-----------------------------------------------------------------|
> |Applications & Software Development                              |
> |DM Solutions Group Inc                 http://www.dmsolutions.ca/|
>   -----------------------------------------------------------------
>



This archive was generated by Pipermail.