Skip to main content

Stop Android SeekBar resetting



I have a ListView in which each item has a SeekBar.





When I update the progress of the Seekbar this is written to a database so it can be reloaded when the application is used again.





Unfortunately if the ListView is scrolled up or down so that any of the items disappear from the visible screen, when they are redrawn they are drawn with the old value.





How do I get the activity to "refresh" when the SeekBar is updated so the values behind the ListView are in sync with the database, this should stop the SeekBar being redrawn with stale data.







@Override

public View getView(int position, View convertView, ViewGroup parent) {

View view = convertView;

try {

if (view == null) {

LayoutInflater vi = (LayoutInflater) mContext

.getSystemService(Context.LAYOUT_INFLATER_SERVICE);

view = vi.inflate(R.layout.task_list_item, null);

}

final Task t = mList.get(position);

if (t != null) {



/* assign layout elements */

final SeekBar seekBar = (SeekBar) view.findViewById(R.id.seek);

final TextView textViewDescription = (TextView) view

.findViewById(R.id.task_description_text_view);

final TextView textViewTaskId = (TextView) view

.findViewById(fyp.proj.R.id.task_id_text_view);

final TextView textViewTaskTitle = (TextView) view

.findViewById(R.id.task_title_text_view);



/* populate layout with task details */

textViewTaskId.setText(String.valueOf(t.getTaskId()));

textViewTaskTitle.setText(t.getTaskTitle());

textViewDescription.setText(t.getTaskDesc());

seekBar.setProgress(t.getProgress());

seekBar.setTag(t.getTaskId());



/* attach listener */

attachProgressUpdatedListener(seekBar);



}

} catch (Exception e) {

Log.i(TaskAdapter.class.toString(), Log.getStackTraceString(e));

}

return view;

}



private void attachProgressUpdatedListener(SeekBar seekBar) {

seekBar.setOnSeekBarChangeListener(new OnSeekBarChangeListener() {



public void onStopTrackingTouch(SeekBar seekBar) {

int progress = seekBar.getProgress();

int task_id = (Integer) seekBar.getTag();



// task handler instansiated with zero as parent project id is

// not needed here.

TaskHandler taskHandler = new TaskHandler(DBAdapter

.getDBAdapterInstance(getContext()), 0);



taskHandler.updateTaskProgress(task_id, progress);



}



public void onStartTrackingTouch(SeekBar seekBar) {

// empty as onStartTrackingTouch listener not being used in

// current implementation



}



public void onProgressChanged(SeekBar seekBar, int progress,

boolean fromUser) {

// empty as onProgressChanged listener not being used in

// current implementation



}

});



}




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