Progress - loading window on NSDocument application - nswindow

I need to show an NSWindow with a progress bar in it while the file is being loaded in an NSDocument application. The makeKeyAndOrderFront: for the "loading progress window" does not seem to be invoked inside readFromURL:ofType:error: since, probably, the app is not fully initialized at that time. What should be the best practice to load a loading progress window in an NSDocument application

After some research, I found this solution That worked fine for me.

Related

CefSharp get screenshot of a page

Is it possible to get screenshot of a web page using CefSharp? I have found information about GetImage() method but it seems to be not supported anymore. Is there any other way? I need to get screenshots from off-screen browser so making screenshot of a screen with browser displayed is not a solution.
I've implemented this feature in a forked branch https://github.com/ivan-sam/CefSharp. This implementation depends on a another commit that fixes script evaluation bug https://github.com/cefsharp/CefSharp/issues/445 , so please clone or download the whole branch.
I've modified CefSharp.Wpf.Example project and added Snapshot button that makes snapshot of the page and opens an image.
If you need to use this feature in WinForms app you can host WPF control with ElementHost

Does Flash Builder 4 Profiler work with a Flex 4.5 project?

I'm trying to use the Profiler for the first time so I don't know much about it. But it doesn't seem to work.
I run my project under profiler, it says it is running, but no window shows up. Nothing. I can see the project's icon down there but I see no window at all.
Can this be cause by the fact that I'm using Flex 4.5? Or am I missing something?
Updated: Here's a screenshot of the Profiler running the an app. You can the app in the dock and it shows its live objects, but I don't see the apps' window and cannot interact with it. The app is just a simple 400x400 window with some black shapes in it.
Thanks in advance,
Nuno
I think your problem is that you may not be running it in a debug player. Check to make sure.
It could be related to this question. It seems the profiler doesn't work well with Flash Player 10.1.

Flex Swfloader with a swf which loads another swf file

I have one Swfloader. This swfloader loads file A.swf.
On creationComplete event, File A.swf loads another swf(file B.swf).
Everything works fine when I run the application once in the same machine.
But when I run two or more instance of the application, the first works fine (both file A and B are loaded) but the second swf (file B) is not loaded by file A.
Could you please help me to find out why the first swf (file A) doesn't load file B, when the application is running in multiple instance ?
Thank you in advance,
Casey
That's weird. There could be a few explanations. First off, have you tried debugging your problem? It could be something to do with browser caching. I would look at your developer console (included with Chrome, ctrl+shift+i, or use Firebug extension with Firefox) in the Net panel to see if it's loading the new swf properly or not.
Are the swf being loaded dynamically with data or is it static (b.swf never changes). There are too many things to take into consideration here, but it could be that there's an error that happening and it's not loading b.swf. Do you have Flash Player debug installed?

clean project in flash builder on debug launch

Using Flash builder 4 to build an AIR app.
I keep having my code changes not take effect when I launch the project with the debugger, probably happens about once an hour. So does anyone know how to have FlashBuilder clean the project automatically before each launch?
Thanks
I'm having a similar issue with a Flex application. If I make a change to an .as file the change is not taking effect. The component is being instantiated by a parent component in the application so the compiler should be catching any changes I made. In fact, I can put a syntax error in the file and it won't report a problem. I've uninstalled and reinstall Flash Builder 4. I have to do a clean every time. I tried the tip from rakslice's comment of compiling with mxmlc manually and it successfully compiled without any clues as to what the issue with incremental compiling in Flash Builder 4 is. I finally added "-incremental=false" to my project's additional compiler arguments. This takes longer to compile of course, but I find it easier than having to click Project --> Clean every time.
I find that as long as I don't change code and/or recompile while an active debug sessions is on-going; I have no issues with the application not picking up code changes between subsequent runs.
I'm finding that I have a very similar problem. Everytime I launch my Flex app in a browser I have to perform a Clean just to get it to run.
I have noticed that I get a JavaScript error saying 'swfobject' is undefined odd error to be getting.
Not sure if that helps?

Visual Studio Play or Build to compile

I recently had a problem with the Issue Tracker starter kit that seemed to be resolved by using the "build" option. Previously, I would typically use the "play" button to debug my app, then just stage the files when everything was working, assuming that the last time I hit the "play" button, it had fully compiled the app.
Anyhow, I'm wondering if there's a difference between the "play" button and the "build" menu option? if so, what are the differences?
The "build" button compiles your website while the "play" button builds and fires up a browser with the default page as an argument.
The "play" button is designed to execute a assembly that is designated in your solution as a starting point. Since an ASP.NET website has no true "entry point" (like static void Main() in a console application) the "play" button simulates a similar action by opening the browser to your projects "start page".
Play button (F5) executes your application in debug mode.
Build menu is only compiles and produces your assemblies.
And one another option, CTRL + F5, it runs your application but not in debug mode.
The downside of "play" with a WebSite project is that you might miss a compiler error if the offending code is outside of the App_Code directory and you don't ever load the code that contains the error. I think doing a "build" does catch those kinds of errors.
Another gotcha to watch out for--if there are additional projects (such as class libraries) within the solution, make sure that the dependencies are set up correctly in the Configuration Manager so that those projects are built before "playing" the site. Otherwise you could make a change in the class library and then "play" the site but not see the change.

Resources