Now I found the fastest solution is assembly. Just like this: __asm__ volatile( “0: \n” “# load 3 64-bit regs with interleave: \n” “vld3.8 {d0,d1,d2}, [%0]! \n” “# swap d0 and d2 – R and B\n” “vswp d0, d2 \n” “# store 4 64-bit regs: \n” “vst4.8 {d0,d1,d2,d3}, [%2]! \n” “subs %1, %1, #1 \n” … Read more
JColorChooser has a getColor method which returns a Color which has methods getRed, getGreen and getBlue respectively solved How to get a RGB value from Color variable
If you get the same values for every pixel there are several possible reasons. a) your image has the same values in every pixel b) you do not change x and y between your calls to getRGB c) you read something else but the return value of getRGB solved getRGB(x,y) in Java awt returns for … Read more
Your current approach is indeed not easily generalizable. The hard-coded parts of the buttons for “blue” and “green”, and especially the special methods like blueToGreen make it impossible to extend the number of colors with reasonable effort. (You don’t want to create methods blueToYellow, blueToRed, blueToTheThirdColorFromThisListForWhichIDontKnowAName …). There are many possible ways of generalizing this. … Read more
What you want to do is add an onchange part to your inputs to handle when the user changes the values of your input sliders. This is what it would look like: <input id=”red” name=”red” type=”range” min=”0″ max=”255″ step=”1″ value=”128″ onchange=”changeColor()”></input> <label for=”red”>red</label> <br> <input id=”green” name=”green” type=”range” min=”0″ max=”255″ step=”1″ value=”128″ onchange=”changeColor()”></input> <label for=”green”>green</label> … Read more
I have to agree with Majid Shirazi regarding the proposed solution by Quang Hong. Let’s have a look at: idx = np.where(img == (0.4, 0.4, 0.4)) Then, idx is a 3-tuple containing each a ndarray for all x-coordinates, y-coordinates, and “channel”-coordinates. From NumPy’s indexing, I can’t see a possibility to properly access/manipulate the values in … Read more