I'm seeing the same thing on Vista64 on a clean install of flexbuilder, specifically the Flex Build Path is blank, and the ant build properties dialog is blank.
Richard
2009-10-27 14:46:56
A:
honestly the best fix I found for it was to just install the flex builder 4 beta, it's free from fb3 owners and is a far superior development environment, fixed all my problems and builds are much much quicker.
Richard
2009-11-02 22:34:53
The beta version is currently available at: http://www.adobe.com/cfusion/entitlement/index.cfm?e=labs_flashbuilder4 FYI, Flash Builder is the new name for Flex Builder.
rakslice
2010-01-17 00:06:13
+2
A:
You are probably running Logitech SetPoint. Try killing all setpoint processes. (you don't even have to restart flex). It worked for me :-S
Scheea
2010-01-05 14:25:33
If it's not SetPoint, look for other software that hooks into other apps' window messages. That could include:- Other software that does keyboard/mouse remapping (like SetPoint) - Diagnostic/debugging tools related to window messages - Macro software that can record/playback key-presses and mouse clicks (like automated software testing suites)
rakslice
2010-01-17 01:07:24
I should add: I suspect that the underlying issue is that bad things happen when the kernel stack is running out of space (http://blogs.msdn.com/alejacma/archive/2009/08/11/controls-won-t-get-resized-once-the-nesting-hierarchy-of-windows-exceeds-a-certain-depth-x64.aspx) and all the hooked-in software is doing is causing a bit of extra memory use for each call. If you _have_ to use a piece of software that hooks others' window messages, you could try other ways around the kernel stack exhaustion (switching to 32-bit windows, or switching to a later version with a bigger kernel stack)
rakslice
2010-01-17 01:21:38
A:
this is happening when you run flex builder on 64bit operating system. i have the same issue.
Sergey
2010-01-07 21:53:32
What makes you think this? I'm running 64-bit and FlexBuilder used to work, but it no longer does. I'm not running anything like SetPoint but I've done many Windows upgrades since I last used FlexBuilder.
Kaleb Pederson
2010-09-27 14:23:39
A:
I had the issue with Window7 x64 Ultimate with FB3 Pro and shutting down Set Point seems to have fixed the issue.
Jim
2010-02-02 22:57:57
+1
A:
According to this Adobe forums post, there are multiple causes:
SetPoint (as indicated by Scheea)
Wacom Tablet drivers
In addition, comments suggest the following:
- UltraMon
These seem to suggest that the cause is any program which monitors keystrokes or mouse movement.
Workaround: In the new wizard dialog above, note the question mark on the bottom left (the help button). When you click on the help button a help panel is added to the dialog on the right separated from the main dialog by a splitter. When you drag the splitter the rest of the dialog appears. You may need to scroll to a position where you can see all of its contents, but it should become usable. Resizing the dialog alone was not sufficient for me.
In addition, I couldn't fully use the mouse to select elements so I had to type into the filter field in order for the correct projects to show up.
Kaleb Pederson
2010-09-27 14:43:49