so I updated my openlayers version from v3.0 to v3.5. I created a feature overlay to be added to my map as a bounding box, for my search extense functionality. I noticed that my feature overlay would disappear from my map whenever my cursor is not directly over my map and reappear when my cursor gets back on my map. This was not the case on the old version of openlayers, v3.0. Anyone knows of the changes that may have caused this issue?
Thanks
Related
I have followed the accessibility example for a Highchart stock chart demo and noticed that sometimes I could access the data points using the arrow keys, and sometimes I cannot.
It turns out when I do not have NVDA running, I can access the data points with the arrow keys, and when NVDA is running, I cannot. I am using the latest version of Highchart's accessibility JS file (version 8.2.2)
I have also noticed this occurs on the demo chart. Has anyone come across this too and have a workaround solution to share?
I'm currently using 3.6.0 and I'm finding that, as features are placed from left to right on the map that features further to the right seem to be offset from their icons - if I place my mouse directly over the graphic feature the mouse cursor (which is wired up to forEachFeatureAtPixel()) does not change until it is moved to the left of the feature icon. On the left of the screen they line up, but it drifts going right until features on the right are completely out of sync.
Any ideas? I thought it may be the library, but I've just rolled back to 3.4.0 and it was the same.
Could this be layout outside of the map canvas bumping items across the screen?
I had the same issue for about a month but in my particular case the problem originated because I was rendering the map while showing a loading panel in front of it wich had a style that caused the web browser to display the scrollbars.
Upon load completion, hiding the loading panel also removed the scrollbar but somehow the map itself didn't refresh properly.
All I had to do was to force map to recalculate the viewport size using the map.updateSize()
http://openlayers.org/en/v3.14.0/apidoc/ol.Map.html#updateSize
I use javaFX 8 with Openlayers 3 in a webview.
Whenever i try to drag the mouse it works for only a small distance (maybe the tile thats loaded on application start?).
After that i seem to grab the entire map tile image (like you can do e.g. in chrome with normal images) and i can move it out of the application screens border.
Because of this i can not move the map around.
Any idea what could cause this or how i could start debugging? Openlayers inspected via weinre throws no js errors it seems, javaFX itself is completely new to me and i get no default errors as well.
Ok, even when you haven't got the problem any more as you are using different tools, for the record:
What for me seems to be working is to define the divfor the map with the ondragstart handler like this:
<div id="map" ondragstart="javascript: return false;"></div>
It seems that in OL 3.1.1 sometimes the start of a drag bubbles up to the WebView as it receives a drag detected event and this starts the image drag. This did not happen in OL 3.0.0
Defining the div like that helped in my case.
I'm using DirectX to allow a user to 'color'/draw in a Win8 app. Much of the drawing code is similar to the Ink Drawing sample that MS has out.
Apologies for the length. I'm struggling to describe the problem briefly.
I'm having issues where, when the user draws a new line in live drawing mode with an InkStroke, that new line is invisible except for a segment being added (while the mouse is moving each finishing segment flashes and then disappears). When I release the mouse it joins my collection of Strokes which render as normal. That is, once you're done drawing a line what you tried drawing looks fine/visible/like you drew it.
I had this working fine as a stand alone C++ desktop app. However, I then connected the SwapChainPanel to an XAML page which also has a Menu. That was when the issue arose. They use the XAML menu to choose an image to color in and the page switches to 'drawing mode' with the desktop app code. The same SwapChainPanel handles context switching on the XAML page and with the drawing buffers.
I believe the problem lies in that the XAML page is using the same SwapChainPanel as the drawing buffers. This is interfering with a call "m_d3dContext->CopyResource(_currentBuffer.Get(), _previousBuffer.Get());" which is how the rest of older part of the 'currently being drawn' line is captured for drawing.
How can I get around this? Is there a solution which would not involve separating it into 2 XAML pages (one for menu, one for drawing), each with their own SwapChainPanel? Even if that is the best way, is there a way to do it with one XAML page?
I am using the ListPicker from the toolkit. I have managed to apply a style template so that when the user is selecting from a list of items in fullscreen mode, it looks somewhat similar to the native WP7 implementation.
However, there are a few things missing that appear on the native implementation:
On full mode enter, the items appear via an animation
When at item is selected, it stays highlighted for an instant, then the items disappear via an animation
Am I missing something or is this simply just not exposed to 3rd party developers using silverlight at this point in time?
Animations are provided in November Toolkit. Download the latest version, please
Check the other posts in the same site .. http://www.windowsphonegeek.com/tips/how-to-customize-the-listpicker-selected-item