I've got a D3 app which uses force to display nodes and links. On my PC, the nodes respond to touch, but on my iPhone, they do not.
My code isn't open source (yet?), but in researching, I noticed this example also doesn't work on my iPhone like it does on my computer:
http://mbostock.github.io/d3/talk/20111116/force-collapsible.html
On the phone, I can drag the nodes; I can zoom in on the graph.. but if I tap the light blue circles, they don't become big blue circles as they do on my PC.
Using Chrome device mode, I tested several different emulated devices. Of the mobile devices, only the Nokia devices worked.
How can I get d3 nodes to respond to touch on mobile devices?
Related
Apparently when you set your device's display size to small react-native-device-info library thought that it's a tablet and according to that all the layouts and everything starting to act like tablets and my images aren't visible anymore. Does anyone having the same problem? Any suggestions?
Okay, I got it. With this new high density phones for example Google Pixel 2 XL or nexus or something like that some phone that you can change your display size to small. When you do that react native behave that your phone is a tablet and showing the tablet layout on that phone. So I actually checked some of the devices densities and there is not a single tablet over 2.0 density.
PixelRatio.get() < 2 ? DeviceInfo.isTablet : () => false
This is working for me if anyone is intrested.
Chromium has this feature Device Mode, and interaction is how it would be on a touch device.
I've tried Safari's Responsive Design Mode, but I don't see a way to emulate touch (without pointer events). It just behaves like I'm using a mouse, but I'd like for it to behave like I'm touching the screen on a mobile device (like in Chrome's inspector).
You can install Apple xCode. After installation, search Simulator through Spotlight.
With Simulator you can open Safari and simulate yours websites with touch control.
You can't. When using Safari on desktop in responsive mode your mouse will only generate mouse events.
Maybe a better solution for your use case than using the Simulator is to use Chrome desktop. When using the dev tools in device mode it will emulate tap events.
when orientation changes in android, native android call the destroy method and total new layout is to be made as far as I know. But I think codenameone doesn't do that which is a great thing. But when I checked the cn1 app in devices while changing from portrait to landscape a blank screen is seen for a while and then the orientation changes.
My Problem is that when I have many more components displayed in a form,
the blank screen appears for a longer duration and sometime it hangs. Does it
happen as I don't use Orientation listener methods etc or is there anything I
can do to solve this issue?
I just tried this on my device and it worked fine for the latest build on my Android 6 device. There was the rotation animation from Android where the screen rotated into its new place.
I'm guessing the rendering of your screen is so slow that Android takes too long to draw it and ends up drawing a black screen instead so it can proceed with the animation.
I can't benchmark an application remotely but I suggest going over the performance of your app and making sure it is truly optimized.
I have a WPF application that includes a screen that users can scroll up and down. It has a scroll viewer control which provides a scroll bar and you can also scroll up and down using touch to drag the content up or down. This all works fine on all of my PCs, laptops and tablets and on most of my clients laptops and tablets.
However, I have one client who can only scroll the form up and down using the scroll bar. Using touch to drag and drop the contents of the form does not work.
I have seen this before on another tablet and we found that by installing all of the Windows updates the problem was resolved. However, on this tablet Windows is saying there are no more updates and the problem still exists.
The tablet is a Linx 10 that had Windows 10 on it from the start - it's not an upgrade. My hunch is that it needs the relevant Windows update but that Windows isn't reporting it as a required update.
Has anyone experienced this and identified what files/updates are needed to resolve it?
Just to re-iterate the application works fine on most PCs and tablets, so I don't think it's a basic coding problem which is why I haven't included any code.
I am developing a Blackberry PlayBook application using Flash Builder 4.6 on a Windows 7, x64 machine. I have installed the Blackberry SDK and generally can test my application with one catch - Rotate Left and Rotate Right options from the menu are grayed out. I don't have the actual tablet (and purchasing one is not a solution) so there is absolutely no way for me to test how the app behaves in the Portrait mode.
Perhaps the problem is the fact that my resolution is 1280x800 without any way to make it bigger (I had expected I'd be able to do this and would just activate the peculiar desktop scrolling mechanism). Is there any solution to this problem?
You can rotate the Playbook emulator in VMWare Player (I use Win 7, 64bit too) - by pulling its black corner with the mouse.
You can check portrait as well as landscape mode both in VMWare simulator.
Playbook OS is designed in that manner to support development on both resolutions , if you have 1280 x 800 resolution you can access right most part by using scroll bar in Vmware tool.
BB Playbook os is designed with some predefined features. like in bottom if you use gesture from left most bottom to right , it will open virtual keyboard , & if you will do the same from right most bottom to left , just like swipe down event . it will change the orientation to landscape to portrait or vice versa.