Search Results

Search found 7 results on 1 pages for 'droidy'.

Page 1/1 | 1 

• Firefox crashes with mulitple Uploadify JQuery browse buttons and ajax

  - by droidy

  Hi, I'm using four JQuery Uploadify browse buttons on a page that's calling the Uploadify code/buttons through Ajax. We have a javascript function called from onComplete which refreshes the Ajax page. The problem we're encountering is that when you start uploading one file, if you click browse to upload another file, Firefox will crash when selecting the second file. Any help is appreciated. Thanks!

  Read the article

• Supporting multiple screen sizes with Android using ImageButtons

  - by droidy

  I've read the Android documentation: http://developer.android.com/guide/practices/screens_support.html but still have some questions. I'm trying to design a music application which basically has images of the instrument (ImageButton) that play a sound when clicked. However, I'm confused about how to have the ImageButtons scale to fit all the different screen sizes and how to position them. Which layout is best used for needing to position ImageButtons in specific locations on the screen? (i.e. cymbals on a drum set) FrameLayout, RelativeLayout? If I only really care about medium and large screens, do I need to create different resources (images) for both as well as a different XML layout to position them? I'm trying to find the simplest way to do this without having to create a separate layout XML file for positioning/size and separate image resources for each screen. Any guidance is greatly appreciated. Thanks!

  Read the article

• Android multiple screen sizes with same density

  - by droidy

  I'm confused regarding the densities. I see that with medium density, the screen resolution could be either 320x480, 480x800, or 480x854. So if I have an image thats 300px wide in the mdpi folder, how is it going to look the same size on all 3 different screen sizes (mainly 320x480 vs the other 2)? And by look the same size, I mean scale to be bigger or smaller depending upon the screen size. Thanks.

  Read the article

• Getting differences between WVGA800 and WVGA854 in Android Emulator

  - by Droidy

  So far I just have one XML layout file, and one drawable directory, drawable-hdpi. I first want to target the high density screens. I added a bunch of imagebuttons to a relativelayout and everything looks perfect in the WVGA800 emulator. The problem arises when I view it in the WVGA854 emulator. Not only do the imagebuttons not position the same, but the images are blurry. I used dip for the layout margins on the imagebuttons even though it shouldn't matter in this case because WVGA800 and 854 are both high density. What is the problem? Why would it look totally different on emulators that have the same density and almost have the same exact screen dimensions? Thanks!

  Read the article

• Why isn't multi-touch working for my imagebuttons?

  - by Droidy

  I'm using imagebuttons that play sounds using SoundPool. Here is example code of one of the imagebuttons: ImageButton Button1 = (ImageButton)findViewById(R.id.sound); Button1.setOnTouchListener(new OnTouchListener() { public boolean onTouch(View v, MotionEvent event) { if (event.getAction() == MotionEvent.ACTION_DOWN ) { mSoundManager.playSound(1); return false; } return false; } }); For some reason, it doesn't allow you to click multiple buttons at the same time. Is it because I'm building for 1.6 SDK? Thanks!

  Read the article

• Android WVGA800 and 854

  - by Droidy

  Although my relativelayout looks very similar on WVGA800 and WVGA854 on the emulator, theres different spacing on some of the objects because I'm going off of marginleft or marginright. Since the 854 is a greater width, its pushing some objects differently. Is there any way I could target either one to adjust for the different margins?

  Read the article

• JQuery Validation Plugin not working when used on page that includes another page via AJAX

  - by droidy

  We have a long page that contains a bunch of different form elements. One part of the form is called remotely via AJAX and is populated in an empty div. This is the part which JQuery Validation plugin is not working correctly on. We have class="required" on the elements on this page, but they do not show up as required. I'm guessing it's because the Validation plugin is looking for class="required" on our main page, and since the content from the AJAX page is put into the empty div behind the scenes, it's not detected the required fields. Any help is greatly appreciated.

  Read the article

1