Balsamiq suddenly keeps reverting back to old screenshot images and moving some icons a little - balsamiq

What the title says. I tried File > Select Unused Images > Delete some images. Seems to still be happening. Can anyone help?

Related

v-icon of vuetify with class 'edit-icon' is not displaying the icon rather it shows the 'edit' text

I am using vuetify 2.2 in my project. In my code, I am using v-icon with class 'edit-icon'. It is supposed to display an edit icon but it is displaying 'edit' as text.
This was working properly but issue started coming once i merged my code to upstream branch. And both the branches have exact same package.config. I even ran my code after npm install but still issue is not gone.
Can someone please guide me to the right direction.
So the problem was indeed with the material icons not being rendered properly as mentioned by #Zim.
This link has the complete list of material icons that can be used.
And in this list, there is no edit icon. Instead they have mdi-pencil for the same purpose. After making that change, I could see the icon being rendered.

White bars at the top and bottom of extension when opened in chrome

I just started developing an extension earlier today and when I checked how it would look within the browser I noticed these white spaces at the top and bottom. I noticed similar but smaller spaces in other chrome extensions I have. I can't seem to find anything online about it. Does anyone know what's going on and how I can fix it?
Here's a picture for reference:
image that shows a picture of extension
The white space at the right side isn't part of the problem it was just the way I captured the picture.
--Question was answered by wOxxOm in comments below.

Fixed Position Rectangles in SSRS 2016

I have a report that is designed to give us a visual representation of available kennel space in our facility. The floorplan image is defined as the background image on a rectangle. Each of the kennel areas are contained in a rectangle on top of the rectangle with the floorplan. I'm happy to share the rdl file if there is a way to upload it to this post (it is 9,559 lines of XML so not practical to copy the code in the post).
When I started into this particular project, I searched for a way to preserve position of each of the report items and the rectangle method came back as the only way to guarantee position at the time the report is generated. I have spent a considerable amount of time making sure each rectangle is positioned precisely where it needs to be on the page. In the designer, when I preview the report, it is as perfect as I can get (note that the image shows the dog lost & found area not lining up as I haven't completed that area just yet). I'm able to zoom in and out in preview and everything stays put exactly where I expect to see it.
On Friday, I decided to publish what I had completed to the server and I'm greatly disappointed at how it looks on the server. I'm at a loss to know how to correct it and can't find anything other than using the rectangles as I have already done. Here is the output on the server:
I even tried it in Internet Explorer and Edge to make sure it wasn't an issue with Chrome. I have not tried Firefox since I don't have it loaded and don't have a need (or desire) to load it. Any ideas as to how to fix this issue are appreciated!

Is this a z-index issue?

I have a menu (this is the menu I'm using with a few modifications: http://multi-level-push-menu.make.rs/) that floats over an image that is linked. Whenever a link is click that is in front of the image, both links are activated.
I've tried added a higher z-index to the menu wrapper, but still not working. Thoughts?
Here is a screen cap of the problem:
http://tinypic.com/r/znoeh2/8
I know the obviously answer is to make the image not clickable, which I will change but I'm concerned this could cause problems somewhere else on the site.

Strange behaviour in my android app (Android 2.3.5) - Things get inflated wrong

I've been experiencing some very strange behavours in an app I'm developing. The app is not very advanced, it stores a couple of places in a sqlite database and is displayed in listviews, on a mapview etc. So, when browsing through my app after deploying it to my phone everything works great, but after a while one listview doesn't get inflated. A scrollbar appears as if the items were there but I can't see them. I push the back button to close the app. When revisiting the app my first view, which has two buttons, gets all messed up. The buttons fill the viewport and the background disappears etc. I can't figure out what's wrong.
Anyone else facing these problems? My phone is a HTC Desire HD with Android 2.3.5
The app is pretty "layout heavy", if you know what I mean. The listview items has custom background images, I'm using custom fonts etc. But the app is running smoothly up to the point when it freaks out and displays/don't display everything wrong.
My first thought is there is some kind of memory issue, ideas?
EDIT:
I believe this might have something to do with defining and using #00000000 as transparent color. Use #android:color/transparent instead.
SOLUTION:
So after doing some testing I found that what I previously mentioned in the edit really is the cause of this problem. I had defined the transparent color in my colors.xml as #00000000. This seems to work, sometimes... And other times it grabs a drawable instead, but not a drawable that is named "transparent", it grabs ANY drawable. Weird but true.
After some testing I finally found the cause of this problem. I had defined the transparent color in my colors.xml as #00000000. This seems to work, sometimes... And other times it grabs a drawable instead, but not a drawable that is named "transparent", it grabs ANY drawable. Weird but true.
So to fix this problem you should use #android:color/transparent instead when you want transparency on, for example, a view background.
If there are memory errors you should be able to catch them in logcat. You'll get "VM failed on xxxx byte allocation" messages (or the like).
Silly/stupid answer: often when I run into layout issues within my app, it's because I needed to do a clean build after having changed my layouts. You might want to start there.
Edit: You might also try the emulator, and if you suspect memory issues you could start the emulator with a small heap to force the issue to occur sooner. You can also check your heap usage in DDMS or with the Eclipse MAT to see if it's leaking.
I was experiencing the same problem on Galaxy tab even with #android:color/transparent. Was able to fix it only by replacing android:background="#color/transparent" with android:background="#null".

Resources