Skip to main content

ImageView showing up in debug mode, but not in run mode



My case is a little special.... I'm trying to get an image via tcp and make it show into my device screen.





Please, don't ask me to do it with another kind of way to get the image, since this is the only way i can do it, and that's not my issue.





What happens is that when i'm debuging step-by-step my program, the image shows up into my screen. But when i run it without debuging, it doesn't show up.





This is my main.xml:







<?xml version="1.0" encoding="utf-8"?>

<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"

android:orientation="vertical"

android:layout_width="fill_parent"

android:layout_height="fill_parent"

>

<TextView

android:id="@+id/textview"

android:layout_width="fill_parent"

android:layout_height="wrap_content"

android:text="Hello World, MyActivity"

/>

<ImageView

android:id="@+id/imageview"

android:layout_width="fill_parent"

android:layout_height="wrap_content"

/>

</LinearLayout>







and this is my MyActivity.java:







public class MyActivity extends Activity

{

/** Called when the activity is first created. */

@Override

public void onCreate(Bundle savedInstanceState) // Aquesta funcio es crida al començar, pero tambe cada vegada que es gira la pantalla.

{

super.onCreate(savedInstanceState);

setContentView(R.layout.main);

}



@Override

public void onStart(){

super.onStart();



TextView tv = (TextView) findViewById(R.id.textview);



try {

Socket s = new Socket("ip-here", port-here);



DataInputStream ins = new DataInputStream(s.getInputStream());



int bytesRead = 0;

byte[] bSize = new byte[10];

while(bytesRead < 10){

bytesRead += ins.read(bSize, 0, 10 - bytesRead);

}

String sSize = new String(bSize);

Integer size = Integer.valueOf(sSize);



byte[] pic = new byte[size];

bytesRead = 0;

while(bytesRead < size){

bytesRead += ins.read(pic, 0, size - bytesRead);

}



Bitmap bitmapimage = BitmapFactory.decodeByteArray(pic, 0, bytesRead);

ImageView image = (ImageView) findViewById(R.id.imageview);

image.setImageBitmap(bitmapimage);



tv.setText(sSize + " -> #" + size + "# -> #" + bytesRead + "#");

} catch (IOException e) {

e.printStackTrace();

tv.setText("error de IO");

}

}

}







Additional information: The TCP server sends a 10-char string containing the size of the image (in base 10). And then the whole image in jpg format.





As you can see, i put a Textbox to tell me what's happening, and it's ok. Even when i run it, it says he got the whole image, but it just doesn't show up...





Am i missing something? maybe i shouldn't put this code in the onStart() method?





Thank you, Víctor


Comments

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex