After perspective
Before perspective
Correct perspective
I am using Inkscape v. 1.0. Here when I am using the perspective extension, it is not likely worked and you see the image after perspective in 2. Actually, the correct perspective is 3. How can I fix this?
It's a bug. Please reply to the questions of the bug triage team in the bug tracker to get it fixed (and to find a suggestion about how to fix it for your case).
https://gitlab.com/inkscape/extensions/-/issues/226
For further bug reports, make sure to subscribe, so you will get email notifications.
Related
Recently I started seeing the following nonsense with the satellite images in my Google Earth plugin:
The incorrect tiles fade in and out as I zoom, and at some zoom levels everything looks fine.
This happens across browsers (chrome, IE9, Firefox), but only on my machine. I've tried re-installing the plugin, but that didn't seem to help.
I'm using plugin version 6.2.2.6613
Does anyone know what might be causing this problem?
I have seen this problem before and again recently. The first time I was told it could be conflicts with the hardware accelerators but then the problem just went away.
Until recently I have had two instances of the plugin running in the same desktop application with no problems. Then a couple of days ago I started seeing the problem again although it is not happening today. I don't know if it would help but I would suggest rebooting your computer.
I've also wondered if Google was updating the plugin or the maps...
Sorry I can't be of any help but I suspect it will go away soon.
It looks like a DirectX issue to me. One possibility to fix is to force the plugin to use OpenGL instead.
You can control whether the plugin usese DirectX or OpenGL by altering the registry key:
HKLM\SOFTWARE\Google\GoogleEarthPlugin\Render\RenderingApi
The allowed values are:
0 (DirectX)
1 (OpenGL)
Try setting the value to use OpenGL to see if it resolves the issue.
Also, if it is a DirectX issue you could try disabling direct3D (as well as and texture acceleration) via the dxdiag as others have suggested.
Finally, you could also try disabling write combing on your card if it is enabled. This is usually done via the display properties for the card you are using.
I found that problem only occurs when I have multiple instances of the plug-in running. Especially if I have it running in two different browsers at the same time.
I found a bug on Plone.org portal (there is totally messed up creating new release for your product), I made a proper screenshot and wanted to submit it somewhere. However, I can't find information where it should be done - is https://dev.plone.org is correct place?
If not - where I should do this?
Yes, https://dev.plone.org/ is the correct location.
Use the Website component when filing a ticket.
There is also a mailing list.
https://lists.sourceforge.net/lists/listinfo/plone-website
It may help draw attention to your problem.
I'm using the Facebook iOS SDK for a project and if I pop a UIViewController after doing a request but before receiving an answer I get an EXC_BAD_ACCESS when it tries to see if the delegate responds to a selector. Well, the delegate is the UIViewController already popped so it probably doesn't exist anymore.
When researching about this issue I stumbled upon this answer here on SO which tell me I shouldn't be having this problem since the delegate is retained. But the answer is a little old and they started to use arc after that. So I checked the SDK and noticed their not retaining it anymore.
Is this a known issue? Am I missing something here?
I tried modifying the SDK and retaining the delegate and the problem disappears. Nevertheless I don't like modifying third-party libraries as I don't have that much expertise and I'm not sure if arc is really a problem in this situation (I thought we didn't need to use retaing/release/autorelease anymore). Also, I thought this being Facebook SDK, if it were a bug someone should already stumbled upon the same problem and solved it.
EDIT: I realize now that at least the version I'm using of the Facebook SDK is not using arc (I don't know if they already support it) and the problem may be this:
#property(nonatomic,assign) id<FBRequestDelegate> delegate;
Shouldn't it be retain?
EDIT2: I'm sorry, I skipped through another answer in the same post linked earlier.
It seems what I pointed out is now obsolete in newer versions of the SDK. The best approach seems to be to cancel the request.
Shouldn't it be retain?
Absolutely not. If you did that then you'd very likely have a retain cycle (VC owning the FBRequest which owns the VC).
You're 100% correct that the right thing to do is cancel the request when the view controller is deallocated, or probably even better is to set the delegate of the request to nil and then cancel it.
I recently decided to run the Resharper 6.0 "Analyze Errors In Solution" option on our web application. After several valid problems it picked up on, it has me stumped on some CSS 'errors':
(disclaimer: I am not a CSS person in the slightest, only understand the principles, so may use the wrong terminology - please bear with me!)
In our web application, we have some CSS selectors which follow this general pattern:
.someselector{
property:inherit
}
This 'inherit' value has been used against the properties of:
padding
border-width
overflow
I realise that the 'inherit' value is not necessarily cross browser compatible, but I'm not worried about that (for now). What I don't understand is why ReSharper is throwing its toys over its use as from what my research shows it is a valid CSS value (albeit not widely supported)?
http://reference.sitepoint.com/css/inheritvalue and http://www.w3.org/TR/CSS2/cascade.html#value-def-inherit
I'm assuming there's something I don't know about the inherit value and its use and would appreciate any enlightenment someone can provide. I am equally happy if an experienced CSS developer can tell me the CSS is valid and ReSharper is wrong. Just looking for clarity of which is right!
Thanks in advance!
JetBrains have already identified this as an issue (and linked to this question!), and have targetted version 6.1 for a fix.
This has been confirmed as a bug (outside of Stack Overflow) and I have lodged a bug report with JetBrains to fix it. The CSS listed above is indeed valid.
I know there have been similar threads in the past but I can't seem to find a decent definitive answer / workaround for the problem I'm facing.
What I'm trying to do:
capture ALT+SHIFT+something keyboard events. Pretty straightforward, right?
Issue:
When pressing ALT+SHIFT doesn't seem to ever shoot an event. The only combination that seems to work with ALT is CTRL+ALT+something, as pointed out here.
Question:
really? I've read that the browser catches some of the keyboard events, but this happens with the basic flash player too - maybe that catches events too? Would love to know if there is a solution that doesn't involve messing with JS.
thank you!
The problem as you've said is that the browser captures some of the key combinations, and the underlying OS may catch others. From the research I've done, and read about on the bug on Adobe's bug base I filed on this, it can be made better if you do an Air app, but even then there are some of these combinations that are just eaten by the OS, so it never even comes NEAR your application.