I know application questions belong on super user but since this is an IDE I thought I might try it here.
For a couple months now, MonoDevelop likes to appear on my second monitor maximized when I start it up. I have to unmaximize it and move it over each time.
I thought it was some weird preference setting I had messed with but I recently install Windows 7 and the first thing I did was get Monodevelop back up and running. It still goes to that second screen.
Anyone know why?
It might be a GTK+ Gdk.Screen issue. AFAIK none of the core MD devs have dual-screen setups - and definitely not on all platforms. Best thing to do would be to file a bug.
Related
I have an acer switch alpha, and both Ubuntu and Debian worked flawlessly with the stylus. But I cannot get it to work at all on Fedora which is my preferred OS.
What works:
Hovering
Clicking on anything related to the gnome-shell (settings, activity bar, title bar) But nothing inside windows aside from the settings application so far.
Very odd behavior, am I missing some libraries?
Honestly the amount of time I waste debugging Fedora over the last few years is a bit much. Never had as many problems on Ubuntu or Debian will probably just swap considering how utterly unreliable Fedora has become.
As of Fedora 25, the distro defaults to booting into a Wayland-powered desktop. Pens are not well supported under Wayland at the moment; only native GTK3 applications such as the shell and GNOME Control Center will react to pen input (many applications either still use GTK2 or another toolkit like Qt).
Until the situation improves, I would recommend using the "gear" icon on the login screen to change your session from "GNOME" to "GNOME on Xorg". The pen should return to functioning as it has in the past.
I'm resubmitting an AIR app to the iOs store after a couple of years. It has mysteriously doubled in size. The android version comes in at just under 30 MB. The ios version is just under 60. I'm trying to figure out if this is something in my code which I should try to track down, or whether this is 'normal' behavior. Has anyone else seen this?
The only thing that I've been able to come up with is that with the advent of Retina, everything has doubled. And/or something to do with iOs7...
Thanks.
Well I did go through Properties - Build Packaging - Package contents and unchecked everything I could. That removed about 4 meg.
But I was building in debug mode. Once I exported a release build, the .ipa was the same size as the .apk generated from the same code. For some reason the debug .apk is nowhere near as bloated as the debug .ipa.
Hope this helps someone else...
I just setup my libgdx game with the gdx-setup-ui.jar today and I have everything setup in eclipse. I thought I would run each application (i.e. desktop, android, and html) to make sure everything is working ok. Unfortunately, I ran into problems with my html application. I am getting this error with a tablelayout.gwt.xml:
I have no idea how to solve this problem. Is there a fix for this problem and if anybody knows it could they share? Thanks!
EDIT
So even though i fixed the problem by restarting my project, my problem has come back. This time, however, I am too far along in development to just restart my project, or re-setup my project.
I deleted my old project and created it again using the gdx-setup-ui.jar application and made sure that all the necessary libraries were included.
When using browseForOpen, browseForOpenMultiple and browseForSave in Adobe AIR, the dialogue that comes up is a bit old-fashioned, and looks like a Windows XP dialog, despite me running Windows 7. It has the Windows 7 border, but I mean the buttons and such look a bit like that of Windows XP.
So I'm wondering, is there a way to make it look more "modern"?
Here's what I mean. Basically, I'm getting this:
But I'd like to get something more like this:
It's not strictly essential, but it's something that's been bothering me for a while and I'd just like to know if it's possible.
the only argument that is available for FileReference.browse() is typeFilter, so I'd assume you can't :P
it probably has to do with the implementation of the method onto the native OS. maybe a native extension could solve the case.
http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/flash/net/FileReference.html#browse()
I recently realised that this only happens when debugging an app. When you actually install the application and browse for files, the windows displays as it should.
I'm not sure if this has always been so and I only noticed it now, or perhaps that an AIR update has changed this.
Irritatingly, Flash Builder refuses to implement any changes I make to the program when I run it. I can't find any documentation of this anywhere online after a brief googling, just wondering if anyone has come across this problem before and/or found a solution? I don't want to have to export a release build every time I want to check if any changes have been implemented successfully (I'm just assuming that'd work)
It happened to me once before but I overcame this problem simply by starting a new project as there wasn't much of any significance, and couldn't easily fix it.
It's pretty much as simple as it sounds tbh, having returned to my computer a couple of hours after leaving it I find any changes to any part of the code have no impact on what is displayed when I go to run...
Any insight would be much appreciated
Thanks
Josh
It could be the cache of your browser. Clear your cache and see if that works..
It could also be because you have classes that are compiled in external swf's. If you compile in Flash Builder, you're not persee recompiling those classes. Instead, compile the external swf which has links to those classes.
You'd think if this were a bug in Flash Builder, people would be complaining about it a bit more often, check that your browser is updating properly, most likely you've got the SWF stuck in your browser cache.
Check the "clear application data on each launch" in Run/Debug Configuration window.
This will clear and uninstall existing app installed in your test device, so every new launch will have clean build.
Tips : Make sure to cmd/ctr + B first, In every run/build.