Databases
StackOverflow2013
Postsdbo
POCustom ImageView, keep state after resize
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POCustom ImageView, keep state after resize
    primarykey
    data
    text
    <p>I implemented a Custom ImageView based on Nicolas Tyler's post here: <a href="https://stackoverflow.com/a/17649895/680488">https://stackoverflow.com/a/17649895/680488</a></p> <p>It works really good but I have one problem:</p> <p>I have the custom ImageView inside a layout with one other layout below the ImageView. This second layout's visibility can be toggled by the user. Whenever this happens, the ImageView gets resized (to fill the whole activity or make space for the other layout). So far so good. The problem is, that when this re-sizing occurs, the ImageView seems to 'lose' its imagematrix and the image is shown again in its original state (zoomed out, so that the whole image fits on the screen).</p> <p>I want to keep the last state before the re-sizing (scroll/zoom back to the same position (or just stay there)). So the question is, when is the best situation to store the imageview's matrix and when to apply it again? (onSizeChanged seems to be to late, right?)</p> <p>I hope it's clear enough...?</p> <p>EDIT: after I implemented it as described in the comments I now have really weird behavior: It first looks good, and the imageView stays at (or actually goes back to) the same state as it was before the visibility change of the other view. However, when I then touch the view to scroll or zoom, it moves a couple of pixels and then jumps to a completely different position and the controls don't work anymore (I cant scroll/zoom). I printed out the matrix values while touching after resizing:</p> <pre><code>OnTouch: 1.204599, 0.0, -1254.761, 0.0, 1.204599, -107.23739, 0.0, 0.0, 1.0 OnTouch: 1.204599, 0.0, -1254.761, 0.0, 1.204599, -107.23739, 0.0, 0.0, 1.0 OnTouch: 1.204599, 0.0, -1254.761, 0.0, 1.204599, -107.23739, 0.0, 0.0, 1.0 OnTouch: 1.204599, 0.0, -1254.761, 0.0, 1.204599, -107.23739, 0.0, 0.0, 1.0 OnTouch: 1.204599, 0.0, -1254.761, 0.0, 1.204599, -107.23739, 0.0, 0.0, 1.0 OnTouch: 1.204599, 0.0, -1254.761, 0.0, 1.204599, -107.23739, 0.0, 0.0, 1.0 OnTouch: 1.204599, 0.0, 0.0, 0.0, 1.204599, -107.23739, 0.0, 0.0, 1.0 OnTouch: 1.204599, 0.0, 0.0, 0.0, 1.204599, -107.23739, 0.0, 0.0, 1.0 OnTouch: 1.204599, 0.0, 0.0, 0.0, 1.204599, -107.23739, 0.0, 0.0, 1.0 OnTouch: 1.204599, 0.0, 0.0, 0.0, 1.204599, -107.23739, 0.0, 0.0, 1.0 OnTouch: 1.204599, 0.0, 0.0, 0.0, 1.204599, -107.23739, 0.0, 0.0, 1.0 OnTouch: 1.204599, 0.0, 0.0, 0.0, 1.204599, -107.23739, 0.0, 0.0, 1.0 </code></pre> <p>so TRANS_X is at once jumping to zero. Any ideas why something like this could happen?</p> <p>Cheers, J</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USjpm
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COhave you tried putting the other view in a separate view from the ImageView? You could try storing the matrix value when the visibility is toggled and then just reapply it after a second.
      singulars
      1. POCustom ImageView, keep state after resize
      1. USNicolas Tyler
    2. COThanks! I don't know why I didn't have the idea of handling it outside the view... I now store the matrix before I set the other view's visibility and then reapply it in the imageview's onSizeChanged(). (If I reapply it right after the new visibility was set, the matrix is reset at some later point). Thanks again!
      singulars
      1. POCustom ImageView, keep state after resize
      1. USjpm
    3. COmhh wasn't as successful as I thought...see EDIT
      singulars
      1. POCustom ImageView, keep state after resize
      1. USjpm
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload