I am using the current Xamarin Studio and trying to get a Core Plot Project up and running.
Importing via the component gallery works perfect.
Now I have scatter graph up and running with zooming and panning working.
I like to have the X and Y axis fixed - always visible - regardless of the displayed range of data.
Setting the IsFloating property on an XPTXYAxis leads to a Crash.
It seems that this is obsolete anyway?
Unfortunately the axisConstraints Parameter is not there - as this seems to be the way to fix the axis on the left or right side of the view.
Any idea how to fix that? Maybe the binding has a problem there?
Related
I am following this tutorial and am unable to make Box Three line up to the top of Box Two (which she shows how to do at around 1:45 in the video).
As you can see in the screenshot, I try setting the top margin to 0 but it has no effect on the layout. If I inspect the value again, I see that it has gone back to 16. I am really unsure what I am doing wrong here as I have been following the video quite closely. The tutorial is quite old from 2016 and I am using the newest version of android studio (bumblebee).
Screenshot of me setting the value to 0 but not having any effect on the display:
How can I make the margin 0??
This is a bug in the latest release: Setting marginTop doesn`t apply when using interface builder, only through XML code. That being said, the issue can be resolved, as you already figured out, by setting the value via 'Declared attributes' from the design view or by declaring the value in your code with
'android:layout_marginTop="0dp"' on your view.
In Box three set height as
android:layout_height="0dp"
then it will will start from top of box two top( both will be equal )
I'm using the emulator with Android Studio, and I'm experiencing the phenomenon shown in the image below.
The problem occurs only when the screen is turned sideways.
It does not happen in the default screen.
I don't know how to solve this problem, and I was wondering if you could tell me something that would help me.
Thank you very much!
You can solve this in three ways:
disable screen rotation - add this to the manifest XML under the relevant activity
android:screenOrientation="portrait"
If you want to go the long and better route it seems to me that you are using a layout that is not constraint layout, the latter supports rotation better, and when constraint correctly what is shown here should not happen.
If all else fails you can use special layout when the screen is in landscape mode, you can read more here:
Android Studio: Creating landscape layouts
Here's a snapshot of my app where you can see the running app which has missing text and you can see the text that should be displaying (which is properly displaying in design mode).
Why isn't the text displaying at runtime?
This only started happening when I updated to version 4.1 of Android Studio and rebuilt my app.
Additionally, here is how they are defined in the layout xml:
Here's a view of the layout details of the one checkbox that is not displaying the text:
Notice that it is showing text size in PT (points).
I changed it to sp after choosing from droplist and now it displays properly.
Not sure why this has always worked in the past and suddenly stopped working.
If it is a change I would expect an auto-update functionality when Android Studio upgrades the project.
Should Not Work In Design Mode Either
If it is a problem I would also expect it to display improperly in the Design Mode also. Instead it looks correct in design mode even though runtime doesn't display it. In this way I would've understood that I was using an incorrect unit.
TextView Also
I found that this was also happening in many of my TextView controls.
Downloaded eval for Teechart for Monotouch iOS. Looks very promising. Could not find documentation though except windows help chm. Are there any docs available on the web?
Also running an example on iPad discovered that pan and zoom are extremely slow unless set to Auto.
chart3.Chart.Aspect.ZoomScrollStyle = Steema.TeeChart.Drawing.Aspect.ZoomScrollStyles.Auto;
Why?
Downloaded eval for Teechart for Monotouch iOS. Looks very promising. Could not find documentation though except windows help chm. Are there any docs available on the web?
Yes, you can download on our web site throught this link.
Also running an example on iPad discovered that pan and zoom are extremely slow unless set to Auto.
Why?
This was the reason we introduced the ZoomScrollStyles property, setting it to Auto, the chart will use the standard zoom and scroll gestures used for iOS (for most common 2D chart styles), meanwhile setting it to Manual, the chart will make use of the default zoom and scroll functionality based on the TeeChart for NET product.
I've been experiencing some very strange behavours in an app I'm developing. The app is not very advanced, it stores a couple of places in a sqlite database and is displayed in listviews, on a mapview etc. So, when browsing through my app after deploying it to my phone everything works great, but after a while one listview doesn't get inflated. A scrollbar appears as if the items were there but I can't see them. I push the back button to close the app. When revisiting the app my first view, which has two buttons, gets all messed up. The buttons fill the viewport and the background disappears etc. I can't figure out what's wrong.
Anyone else facing these problems? My phone is a HTC Desire HD with Android 2.3.5
The app is pretty "layout heavy", if you know what I mean. The listview items has custom background images, I'm using custom fonts etc. But the app is running smoothly up to the point when it freaks out and displays/don't display everything wrong.
My first thought is there is some kind of memory issue, ideas?
EDIT:
I believe this might have something to do with defining and using #00000000 as transparent color. Use #android:color/transparent instead.
SOLUTION:
So after doing some testing I found that what I previously mentioned in the edit really is the cause of this problem. I had defined the transparent color in my colors.xml as #00000000. This seems to work, sometimes... And other times it grabs a drawable instead, but not a drawable that is named "transparent", it grabs ANY drawable. Weird but true.
After some testing I finally found the cause of this problem. I had defined the transparent color in my colors.xml as #00000000. This seems to work, sometimes... And other times it grabs a drawable instead, but not a drawable that is named "transparent", it grabs ANY drawable. Weird but true.
So to fix this problem you should use #android:color/transparent instead when you want transparency on, for example, a view background.
If there are memory errors you should be able to catch them in logcat. You'll get "VM failed on xxxx byte allocation" messages (or the like).
Silly/stupid answer: often when I run into layout issues within my app, it's because I needed to do a clean build after having changed my layouts. You might want to start there.
Edit: You might also try the emulator, and if you suspect memory issues you could start the emulator with a small heap to force the issue to occur sooner. You can also check your heap usage in DDMS or with the Eclipse MAT to see if it's leaking.
I was experiencing the same problem on Galaxy tab even with #android:color/transparent. Was able to fix it only by replacing android:background="#color/transparent" with android:background="#null".