I'm using a PHP script which expects user input from a command like fgets(STDIN). The problem is it no longer works in the newest version of PHPStorm (10).
The same works when I run it directly (without debugger enabled) and anything I enter in the console is sent to the script (on direct run).
But during a debug session, when I try to input text at the script's prompt, it does not go to the script. My best guess is that the new REPL feature is overriding user input in console during debugging. I say this because pressing the UP/DOWN arrows opens up a popup with all PHP function names.
It used to work correctly with last version.
How can I send user input to my PHP script with this new version? Am I missing something here?
I'm not sure if this is the same thing, but I was running into this same problem, and I was able to get it working by deselecting the "Use Console Input" checkbox in the PHPStorm Console.
John's answer is perfect.
I want to mention that the Use Console Input is a tiny icon in sidebar of the debug console. I provide you by this image
I recently upgraded from MySQL Workbench 5.2.47 up to 6.1.
After making changes to a table via the Gui grid interface on the old version, I'd hit the 'Apply' button and have a popup confirming to make the change. This popup had the SQL code that would run in order to make the change that I made via the UI interface. I would then confirm the action and get a success or failure popup. If a an error occurred, I could see the detailed error in order to easily troubleshoot the problem.
With the new version, I make a change in the GUI interface and hit the 'Apply' button. No confirmation popup, it just executes. The result is a small snippet in output window. This is fine unless there's an error, in which case it has a very generic message. "1 error(s) saving changes to table XYZ". I have not found how to access the detailed error message, either by right clicking the row or looking in the preferences.
So, how do I get the popup confirmation with SQL query and error messaging to work in the new version or, at the very least, be able to see detailed SQL query error details?
Functionality restored in CE release: 6.1.7
http://dev.mysql.com/downloads/file.php?id=452662
It is indeed a bug :-(
In the MySQL bug database:
http://bugs.mysql.com/bug.php?id=72169
http://bugs.mysql.com/bug.php?id=72155
Until they don't fix the bug you can try to close the Query Tab. When it asks if you want Save the Changes or Not, you choose Save and then it shows the detailed errors :)
I've set up a FlexUnit test on my Adobe Air project and want to test some functionality that uses NativeProcess. When I run the test it gives this error:
Error: Error #3219: The NativeProcess could not be started. 'Not supported in current profile.'
This is because the FlexUnitApplication-app.xml doesn't have this line enabling NativeProcess:
<supportedProfiles>extendedDesktop</supportedProfiles>
The problem is that FlexUnitApplication-app.xml gets auto generated each time it builds without that line.
I've been able to get it to work by running the test using "Run all tests" from the FlexUnit Results window and letting it fail. Then I add the line to FlexUnitApplication-app.xml in bin-debug and running the tests again. If anything in the project changes I need to repeat these steps so this isn't ideal.
You need to add it to your launch profile: click on the little arrow next to the bug icon and select Debug Configurations (or select the project properties > run/debug settings)
Choose the launch configuration you want to edit on the left of the new dialog. In the "main" tab of this config, the last option is "Profile", you can switch between "desktop" and "extendedDesktop" there.
Do you guys know how to activate the n-th Google Chrome window with Applescript? For example, if I have three Google Chrome windows opened, how do activate the second?
I've tried many different combinations, e.g.:
tell tab 3 of window 2 to activate
I've also noticed that:
tell application "Google Chrome"
tell window 1 to activate
end tell
and,
tell application "Google Chrome"
tell window 2 to activate
end tell
produce the same results, it only activates the last window
opened, Is this a bug?
Thanks in advance :)
tl;dr
Using set index of window <n> to 1 isn't fully effective in that it doesn't truly activate the window - it does make it visible, though.
Workarounds (examples assume you want to activate window 2):
Yar's answer offers a pragmatic workaround, though it's not entirely clear why it works. It does, however, have the advantage of not requiring the calling application to be authorized for assistive access, unlike the following solutions.
user495470's answer hints at a robust and generic solution that also works with non-AppleScriptable applications:
tell application "System Events" to tell process "Google Chrome"
perform action "AXRaise" of window 2
set frontmost to true
end tell
Alternatively, use the AppleScript handler defined below as follows:
tell application "Google Chrome" to my activateWin(it, window 2)
While adayzdone's answer should work and almost does, there is a catch - which may or may not be a problem (observed on Chrome 21.0.1180.89 on Mountain Lion) [update: still applies as of Chrome 47.0.2526.106 on OSX 10.11.2]:
While the solution will show the desired window as the front window, Chrome will NOT treat it as the front window if a different window was previously active. You can tell by the inactive close/min/zoom title-bar buttons, by what window title the checkmark is next to, and by the fact that keyboard shortcuts such as Cmd-L will not apply to the desired window.
If your next action will be to click somewhere on the window anyway, this may not be a problem, as such a click will fully activate the desired window.
Otherwise, you can employ a reasonably robust GUI-scripting workaround (gratefully adapted from a generic solution here):
Update: Sadly, the problem of not actually activating the window whose index you set to 1 seems to affect ALL apps (experienced on OS X 10.8.3).
Here's a generic function that properly activates a given window in a given AppleScriptable app using GUI scripting.
# Activates the specified window (w) of the specified AppleScriptable
# application (a).
# Note that both parameters must be *objects*.
# Example: Activate the window that is currently the 2nd window in Chrome:
# tell application "Google Chrome"
# my activateWin(it, window 2)
# end tell
on activateWin(a, w)
tell application "System Events"
click menu item (name of w) of menu 1 of menu bar item -2 ¬
of menu bar 1 of process (name of a)
end tell
activate a
end activateWin
On a side note, what the OP tried - e.g., activate window 1 - seems to be broken in ALL apps on OS X 10.8.3 as well - while the underlying application is activated, the window spec. is ignored.
Here's the original, more didactic code:
tell application "Google Chrome"
# Each window is represented by the title of its active tab
# in the "Window" menu.
# We use GUI scripting to select the matching "Window" menu item
# and thereby properly activate the window of interest.
# NOTE: Should there be another window with the exact same title,
# the wrong window could be activated.
set winOfInterest to window 2 # example
set winTitle to name of winOfInterest
tell application "System Events"
# Note that we must target the *process* here.
tell process "Google Chrome"
# The app's menu bar.
tell menu bar 1
# To avoid localization issues,
# we target the "Window" menu by position - the next-to-last
# rather than by name.
click menu item winTitle of menu 1 of menu bar item -2
end tell
end tell
end tell
# Finally, activate the app.
activate
end tell
Try:
tell application "Google Chrome"
activate
set index of window 1 to 1
delay 3
set index of window 2 to 1
end tell
As mklement mentioned, changing the index raises the window, but for example keyboard shortcuts are still registered by the previously frontmost window.
tell application "Google Chrome"
set index of window 2 to 1
end tell
Another option is to tell System Events to AXRaise window 1:
tell application "Google Chrome"
set index of window 2 to 1
end tell
tell application "System Events" to tell process "Google Chrome"
perform action "AXRaise" of window 1
end tell
Set the index and then open Chrome.
tell application "Google Chrome"
set index of window 2 to 1
delay 0.01
do shell script "open -a Google\\ Chrome"
end tell
Source
In addition to the solutions regarding activating the desired window, (at least) newer Chrome versions also support windows’ active tab index property:
tell window 1
set active tab index to 5
end tell
if you run this
activate application "Google Chrome"
tell application "System Events" to keystroke "`" using command down
it will do the whole thing even if its run from script editor.
heres another way, this one was already spelled out by someone else just in more steps:
tell application "System Events" to tell process "Google Chrome" to perform action "AXRaise" of window 2
activate application "Google Chrome"
if youre willing to save it as an application and assign it to a hotkey, you can do this:
tell application "Google Chrome" to set index of window 2 to 1
though i suppose at that point you may aswell simply hit command+`. Unless of course, your applescript involves a series of steps creating a series of steps, as is likely the case. If it involves a series of steps, something like the first line of the second code sample would be all you'd need, provided you assign it to a hotkey and hit the hotkey when chrome is already activated (or the line comes after chrome is activated in your code).
I've just created a console application. If I run it from the command line, no problem - I can see my output. But if I run from within MonoDevelop, no application output window appears.
I restarted MonoDevelop and that had no effect.
Any suggestions?
And the answer is somewhat illogical (hence why multiple people have this question).
In the Options for the project, on the Run tab, there is a checkbox for "Run on external console." If this option is cleared, the Application Output window will come back when you run the project, and will the become available from the View -> Pads submenu.