I've got problem with alternative mode displaying in FAR manager. When switching to it with Win+A or lock icon in menu it displays nothing. It begun after one of the updates of the conemu.
Conemu version is 160914 stable
Far version is 3.0.4455 x64
Conemu plugin in FAR is avaliable and works fine
With the help of Maximus I found that after update the setting Inject ConEmuHk in Settings->Features tab was unchecked. So this was an issue
Related
I have copied the project from my old amchine to windows 10 machine. Application works without any problem on simulator. If I right click to see the properties, I don't see IOS, Android and build hints. Please advise if there is something I'm missing here.
This was removed ages ago in Codename One 5.0 but was deprecated before that. See https://www.codenameone.com/blog/removing-old-preferences.html
You should use Codename One Settings in the right click menu.
I have a strange problem I need some help with.
Very recently I started experiencing a problem with the hamburger/side menu.
On startup our production version renders the hamburger menu in black but the current dev version renders in blue.
Once I login on the dev version, and start using the app, when I go into one of our application's forms, the hamburger menu disappears. The side menu can be activated by a slide-in motion.
I first started seeing this when doing a cloud/device build, not on the simulator.
A day or so after I got this on the simulator.
Thinking it may have been an environment issue (specifically I had been doing some theming with the GUI designer), I set everything up on my Windows VM, with a clean copy of the production code copied out of SVN - but I get this problem on the 'clean' version.
As I inherited this code, I was able to go back to the machine left by the previous developer and in running their version in the simulator all was fine. Black hamburger on login screen and present on our application forms.
I submitted the code to do a SAAS device build but then a library update ran on this previous developers machine, and I now get blue Hamburger at startup and missing on our application forms in the simulator - the same problem that I got.
Seems to point to something in the new libs. So, I then pegged the versioned build back a level (3.6 rather than latest) - to try to resolve any 'new version' issues but I get the same problem.
I guess we are missing some initialisation steps out on the new sidemenu - our code has been in place for a few years now, so ideally I would like to build against the previous version of the CN1 libs where we didn't have this problem until I have time to work what we are missing.
I thought versioned build would give me this ability but the problem persists- any assistance would be gratefully accepted.
UBUNTU 16.04
Windows 8&10
Eclipse Oxygen
We transitioned to the on-top menu over the weekend. This has been announced a while back and despite that as usual people were caught a bit off guard. We posted multiple updates on that to the blog so you should probably keep an eye on that.
The on-top side menu uses the default TitleCommand UIID styling where the old side menu had a different UIID but I'm guessing the engineer in charge used the theme constant sideMenuImage which we didn't include in the first release of on top side menu. This should be fixed in the update coming out this Friday (November 3rd 2017).
FYI You can disable the on-top mode using Toolbar.setOnTopSideMenu(false) although I would recommend sticking with it as it's WAY better.
So I just updated to IE10. When I try to debug my web app's javascript, my breakpoints are all just outlines with a little triangle and say in the tooltip:
The breakpoint will not currently be hit. No symbols have been loaded
for this document.
IE10 is started when I start debugging and it goes to the website like IE9 always did. If, in VS 2010, I go to Debug > Attach to Process... and select the iexplore.exe process, as my javascript executes it will hit and stop at breakpoints like it always would with IE9 and everything is peachy until I kill IE10 and start debugging again.
I've made sure that Javascript Debugging is enabled in IE10 and any "solutions" I find online all say to uninstall/reinstall VS2010/IE10 and see if that helps. I already know that VS2010 is capable of debugging, it's just not attaching the debugger properly. How can I fix this so that debugger attaches properly and will hit breakpoints and exhibit the usual behaviour?
Another StackOverflow Post recommends installing VS2012 (any version) and that should fix your issue when debugging JavaScript in IE10 with VS2010.
This may fix JavaScript debugging issue in IE10:
Close Internet Explorer
Press start and type CMD
Run one of these commands in command prompt
32-bit OS
regsvr32.exe "%ProgramFiles(x86)%\Common Files\Microsoft Shared\VS7Debug\msdbg2.dll"
64-bit OS
regsvr32.exe "%ProgramFiles%\Common Files\Microsoft Shared\VS7Debug\msdbg2.dll"
There is another thread on this issue, as Elijah mentions, and this answer is probably more appropriate there, but that thread is closed to me because I'm a new poster. Corey has already mentioned that he can't install VS2012 at this time, but it may be useful to others.
I experienced this same problem after updating to IE10. I already had VS2010 and VS2012 with Update 1 installed, and none of the recommended fixes (including the msdbg2.dll registration) worked for me. What fixed my problem was to reapply Update 1 for VS2012, choosing the "Repair" option. I can now debug javascript in VS2010 again.
I use XCode 4.6 on OSX 10.8.2 and the "Show in Finder" Function from the right click context menu that used to work doesn't work anymore on my box. It just does nothing. I tried an XCode restart, restarting the machine, without success.
Can anyone imagine a way how this could be fixed without a fresh XCode install?
Note: Does work for my other Applications, iTunes for instance.
I am not sure what the actual issue is but whilst having a look around on the superuser.exchange website I came across this https://superuser.com/questions/479476/show-in-finder-wont-open-a-new-finder-window which seems to be what your issue could be.
Glad it has helped.
I have a WPF 4 application running on Windows XP. When I run Snoop, it picks up the application, however when I click on "Snoop this application" nothing happens. Also when I click on the magnifying glass nothing happens.
Any ideas?
If you are running your application in administrator mode then Snoop will not work unless you don't run your Snoop in administrator mode , so better check what privilege you have given to Snoop.
The new version of Snoop supports WPF 4 (http://www.cplotts.com/2010/02/14/snoop-now-supports-wpf-4-0/).
Which version are you using?
The latest and greatest version of Snoop is always available at http://snoopwpf.codeplex.com.
One thing to note is that the source code (available for download) is usually somewhat out of date ... as compared to the released bits which you can download an installer for. That is, I don't release Snoop for every fix/change I make.
For example, the currently released version is v2.6.0 ... but I have 9 work items marked for v2.6.1. Check out the Issue Tracker for more info on what is in each version.
I have had the same problem, but only with the msi (the installer). So, I downloaded the source code and rebuilt Snoop on my machine, and after this, it all works fine.