I'm using ImageLoaderCallback and calling imageviewer.showImage(Uri uri).

It's working for all URLs except some. Like this one :

Code :

        bigImageView.setImageLoaderCallback(new ImageLoader.Callback() {
            @Override
            public void onCacheHit(int imageType, File image) {
            }

            @Override
            public void onCacheMiss(int imageType, File image) {

            }

            @Override
            public void onStart() {
                Helper.log("start : " + getClass().getName() + url_base);
            }

            @Override
            public void onProgress(int progress) {
                if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.N) {
                    progress_load_bing.setProgress(progress, true);
                } else {
                    progress_load_bing.setProgress(progress);
                }
            }

            @Override
            public void onFinish() {
                bigImageView.setVisibility(View.VISIBLE);
                loadingView.setVisibility(View.INVISIBLE);
                set_wall.show();
                show_info.show();

                try {
                    sheet = new InfoSheet(
                            title.split("©")[0],
                            title.split("©")[1],
                            view_link,
                            view_link);

                    if (!WallpaperSetter.this.isFinishing())
                        sheet.show(getSupportFragmentManager(), "info_shit");
                } catch (Exception ignored) {
                }
            }

            @Override
            public void onSuccess(File image) {
                imageFile = image;
            }

            @Override
            public void onFail(Exception error) {
                Toast.makeText(WallpaperSetter.this, "Error Loading Image", Toast.LENGTH_SHORT).show();
                error.printStackTrace();
            }
        });
        String bet = BingActivity.getNextImage(url_base, BingActivity.Res.getByOrder(index));
        Helper.log(bet);
        bigImageView.showImage(Uri.parse(bet));

PS: I couldn't get the printing statements executed from onStart

Hey, thanks for creating this! It's super helpful for loading big images.

Unfortunately, I'm not sure if I can use BigImageViewer to load encrypted images. I'm successfully loading encrypted images using Glide with a custom ModelLoader that decrypts the images during Glide's decoding step, but these images are not large enough that I need to use BigImageViewer. In a separate view in my app, I'm displaying images that can be quite large, so I'm hoping to use BigImageViewer to display them. All images in my app must be encrypted on disk.

Is it possible to use BigImageViewer with a GlideImageLoader that uses a custom ModelLoader? If not, could you think of any other way I could decrypt image files while presenting them using BigImageViewer?

This PR adds a new kind of GlideImageLoader class called GlideCustomImageLoader which allow the consumer of the lib to specify a concrete GlideModule associated with a previously registered glide component. That way, the lib is able to load resources as the client specifies, in the example added we request an specific image size by appending two parameters at the end of url.

Regarding implementation, I've opted to make a new class instead of adding code to the original one (that was my first approach) and messing the code, hope it's the less invasive as possible.

Good day Sir I am a graphic designer and i am interested in designing a logo for your good project. I will be doing it as a gift for free. I just need your permission first before i begin my design. Hoping for your positive feedback. Thanks

Getting issue android.view.InflateException: Binary XML file line #0: Binary XML file line #0: Error inflating class com.github.piasy.biv.view.BigImageView when using it

Try creating sample app

and use maven { url "http://dl.bintray.com/piasy/maven" } compile 'com.github.piasy:GlideImageLoader:1.4.6' compile 'com.github.piasy:BigImageViewer:1.4.6' compile 'com.github.piasy:ProgressPieIndicator:1.4.6'

`<android.support.constraint.ConstraintLayout xmlns:android="http://schemas.android.com/apk/res/android" xmlns:app="http://schemas.android.com/apk/res-auto" xmlns:tools="http://schemas.android.com/tools" android:layout_width="match_parent" android:layout_height="match_parent" tools:context="android.hackernewsak.com.myapplication.MainActivity">

<com.github.piasy.biv.view.BigImageView xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:app="http://schemas.android.com/apk/res-auto"
    android:id="@+id/mBigImage"
    android:layout_width="match_parent"
    android:layout_height="200dp"
    app:optimizeDisplay="false"
    app:failureImageInitScaleType="center" />

</android.support.constraint.ConstraintLayout>`

BigImageViewer.initialize(GlideImageLoader.with(getContext())); BigImageView bigImageView = view.findViewById(R.id.mBigImage); bigImageView.setProgressIndicator(new ProgressPieIndicator()); bigImageView.showImage( Uri.parse("sone url"));

I am using setOnClickListener on BigImageView. It will trigger click listener fine if I load image from local but if I load online image and it fails to load, then click listener is not working because it is actually trying to load the image again instead of triggering click listener.

When I walk through the code, I think this line is causing problem. For normal use case it is fine but I think there must an option to disable retry on image click so that user can listen to it.

Or If I am wrong then guide me how to implement onclick for failure image use case.

Currently I achieved this by ImageLoader.Callback and override onFail function.

GlideProgressSupport.DispatchingProgressListener.LISTENERS静态变量,即使调用forget方法,还是会导致承载BigImageView的activity不能释放,造成内存泄漏. 我是用eventbus来解决的,如下:

https://github.com/hss01248/ImageLoader/blob/master/image/src/main/java/com/github/piasy/biv/view/BigImageView.java https://github.com/hss01248/ImageLoader/blob/master/glideloader/src/main/java/com/hss01248/glideloader/big/GlideProgressSupport.java

用jdk里的订阅者也可以,就是有点繁琐.

I try to use saveImageIntoGallery() to save an image to the device's gallery, it works fine on android < 10 with a timestamp as a filename and correct extension. However, when I try on a device with android >= 10, the filename was not the timestamp anymore and the extension will be ".0" which I think came from the filename on the cache.

This problem occurred on Samsung and OPPO devices, but not on the Pixel emulators(because it appends .jpg to the saved filename)

implementation "com.github.piasy:GlideImageLoader:1.6.7"

with minSdkVersion <17 gives

Manifest merger failed : uses-sdk:minSdkVersion 16 cannot be smaller than version 17 declared in library [pl.droidsonroids.gif:android-gif-drawable:1.2.20]

by the way, how did you even fit the minSdk 17 library into minSdk14 library? interesting.

Hi, this is the work I did to make BigImageViewer better support shared transition animations, this is all working and tested, but this is only a starting point.

The problem, as described in #98, is that while the animation is running between two activities, the View switches the thumbnailView and the SSIV, causing stutters, or black frames, or an animation that does not run at all.

My suggestion is to have an additional parameter to only show the thumbnail for the transition and delay the main image loading, so we can trigger it later using listeners.

I've made those modifications, and a test environment, using two activities and it does work, while not breaking the others activities in the sample app.

I've added another listener for testing purposes, tell me if you want to keep it or not.

While working with the sample app, I reduced the number of warnings, moving harcoded strings in resources and other stuff, hope you don't mind. Bumped okhttp to the next minor too.

What do you think? would you do it in a different way?

Good night for now.

In my app I use OkHttpImagePipeline instead of standard one, but BigImageViewer breaks this configuration and returns everything to default. How to prevent it?

UPD: I noticed, that I can set my configuration into BigImageViewer initialization, but I don't understand, why do you repeat Fresco initialization again inside FrescoImageLoader...

I came on here as my app was crashing on Android 11 due to the jpg/jpeg issue, but am I right in saying that ALL images are saved as jpeg? My app serves up images as either webp or animated gif images so would be good if I was able to save in these formats, either by auto-checking the filename, or forcefully choosing the mime type in the code.

Possible?

Thanks.

I can see that the library has migrated to AndroidX, which is great. However, when we turned off Jetifier, we found out that one of the dependencies of ProgressPieIndicator still depends on the old support libraries, namely com.github.filippudak.progresspieview:library. I have forked the project and pulled PR https://github.com/FilipPudak/ProgressPieView/pull/18. Unfortunately, the project looks dead, so, maybe it is better to create new maven artifact from my fork.

App crashes when we try to load a new image URL on failure callback:

You can't start or clear loads in RequestListener or Target callbacks. If you're trying to start a fallback request when a load fails, use RequestBuilder#error(RequestBuilder). Otherwise consider posting your into() or clear() calls to the main thread using a Handler instead.

Is it possible to load images with POST request instead of GET. I can not find anything to pass custom request object other than Uri.parse.

BigImageView bigImageView = (BigImageView) findViewById(R.id.mBigImage); bigImageView.showImage(Uri.parse(url));