Custom Query
Results (289 - 291 of 3893)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1649 | Rejected | Multiline strings without the "& _" | Jon | JRowe |
| Description |
This would be very useful to alleviate several cases where multi-line strings are useful, and the & _ syntax becomes clumsy or even difficult to work with. It helps in both coding and making code readable. I've been using multiline strings for string manipulation, in the building of MySQL queries, document parsing, in AuCGI, and various other areas. $s_String = "This is a test." & _ "This is a continuation of the test." & _ "The ideal behavior for multi-line strings would be to emulate the appearance in the code file." ConsoleWrite($s_String & @LF) ConsoleWrite(@LF) $s_String = "This is another test." & @LF & _ "This is a continuation of the other test." & @LF & _ "New lines should implicitly have @LF or @CR." ConsoleWrite($s_String & @LF) This is how I'd expect to write a multiline string - this would be very useful and save lots of time. $s_String = "This is What I'd expect to write. Another line. The string would be an exact match to what's written here, with no awkward & _ syntax." |
|||
| #1650 | Rejected | Problem with Run("psexec", .., $STDERR_CHILD + $STDOUT_CHILD) on Vista 64bit | Jon | HighGuy |
| Description |
Hi, the following code with the current version 1.98 of the Sysinternals tool psexec works fine on my XP SP3 pc but not on my Vista 64bit where it produces a stucked cmd window:
Run("psexec.exe Hint: if i remove the parameters $STDERR_CHILD and $STDOUT_CHILD it will not stuck any more. Starting psexec in a cmd-Shell works fine as well. Thanks in advance for analyzing this issue, HighGuy |
|||
| #1656 | No Bug | Object not being released properly | Jon | FuryCell |
| Description |
The following code should release the iTunes object so a dialog about scripting being in use by iTunes will not appear. However it does not seem the object is released properly as iTunes still complains. Global $oiTunes=ObjCreate("iTunes.application")
ObjEvent($oiTunes,"_Event_")
While 1
Sleep(100)
WEnd
Func _Event_OnAboutToPromptUserToQuitEvent()
Global $oiTunes=0
EndFunc ;==>_Event_OnAboutToPromptUserToQuitEvent
From the iTunes documentation The ITEventAboutToPromptUserToQuit event is fired when iTunes is about prompt the user to quit. This event gives clients the opportunity to prevent the warning dialog prompt from occurring. If the user attempts to quit iTunes while a client still has outstanding iTunes COM objects instantiated, iTunes will display a warning dialog. This event is fired just before the warning dialog is shown. iTunes will then wait up to 5 seconds for clients to release any outstanding iTunes COM objects. If all objects are released during this time, the warning dialog will not be shown and iTunes will quit immediately. Otherwise, the warning dialog will be shown. If the user chooses to quit iTunes anyway, the ITEventQuitting event is fired. See _IiTunesEvents::OnQuittingEvent() for more details. |
|||
