Exception while using SelectDirectoryDialog (TSelectDirectoryDialog) in Free Pascal / Lazarus - lazarus

I just wanted to test the "SelectDirectoryDialog" as described on the resource page: TSelectDirectoryDialog, the linked doc page is currently down. But I'm getting an exception "External:SIGSEGV". Not sure what I'm doing wrong here. I put the "SelectDirectoryDialog" on the form and created a button that executes the following code:
procedure TForm1.Button1Click(Sender: TObject);
begin
if SelectDirectoryDialog1.Execute then ShowMessage(SelectDirectoryDialog1.FileName);
end;
I looked up a few examples (here, here and here), but I can't find anything that's wrong with my code. I tried the TOpenDialog, that one works without a problem.
Any ideas how to fix this? Is there a different dialogue that let's me select a directory as a quick fix?
Update:
The problem seems to be with the debugger, here's a thread describing it. Executing the Exe-File works fine. Does anyone know if the more current Version have a fix to this? (I'm using Lazarus V1.6 from 2016, FPC-V. 3.0.0, SVN-Revision 51630 - the 64bit Version).

Not sure if it the problem, but did you try menu -> Tools -> Options -> Debugger -> check the checkbox for DisableLoadSymbolsForLibraries ?

Related

UFT 14.x cannot execute ctrlC+ctrlV in IE

I need a solution for this error
Before using UFT 14.x , I wrote my code on UFT 12 (on windows 7) for copy/paste function. (It worked 100%)
When I upgraded UFT to 14.x , that function respond with an error . The code and the image are the following :
Function WritingFast(strDataTable)
set objCB=createobject("Mercury.Clipboard")
objCD.Clear()
objCD.SetText (strDataTable)
Window("Internet Explorer").WinObject("Internet Explorer_Server").Type micCtrlDwn + "v" +micCtrlUp
objCB.GetText
End Function
The error says that WinObject("Internet Explorer_Server") is not unique, what are you trying to refer to by this object?
Please examine the description of the object in the object repository in order to see why the description there isn't enough to make it unique.
Alternatively you could take a step back and think about what you're trying to do, perhaps UFT's web support allows you to do it directly and not by trying to access the underlying Win32 objects.
Can't add a comment, rules, sorry. Gonna put has an answer but its more a tip.
If you don't have a duplicate, try capture the object again. See if UFT recognize that object exists or not at your repository.
At least you can see what he is capturing whit the upgrade and compare (if different).

Not able to see the results by using Dbms_Output.Put_Line

I am not able to see the results by using Dbms_Output.Put_Line in sql developer. The result is shown only once. When I execute it again, it is not shown.
I checked a lot of workarounds described in google, but those haven't worked for me.
I am executing following:
set serveroutput on;
BEGIN
Dbms_Output.Put_Line('hello1');
END;
It should print 'hello1', everytime it executes, but instead, it does so only during first run. I have also tried the only resolution available on google:
Opening the 'view' menu and clicking on 'dbms output'. I got a dbms output window at the bottom of the worksheet. I then added the connection by clicking on plus sign appearing in window. But even that did not work for me.
Please can anyone help me here?
The version your are using, 3.0.02.83, was an early-adopter (i.e. beta) release. There seems to have been at least one known issue with dbms_output in that version, and this looks like an extension of those problems. As noted in comments, the behaviour you are experiencing in that old version isn't reproducible now.
Unless you have a pressing need to be on an old unsupported beta version, you should upgrade to a later release. At the time of writing the current version is 4.1.0.19, and you can get that from the SQL Developer downloads page.
This version is being used at my workplace and is remotely hosted, so there is a remote possibility that they will upgrade by acting on my advice.
For now I am able to generate output by this simple workaround:
To generate the output I have to select and run all the statements(including 'set serveroutput on;') as a whole, every time I need to generate output. Note that executing 'set serveroutput on;' and
BEGIN
Dbms_Output.Put_Line('hello1');
END;
separately is not working. I need to select the statements at once and run together in one Go. That's the way it is working for me.

Firefox bug with Selenium - Can't access dead object

I've tried to run my tests with Selenium 2 and Firefox 19. One of this tests causes an error "ERROR: Command execution failure. The error message is: can't access dead object".
I'm reading about it, it seems like a bug in newest Firefox's versions. Lot of people have the same issue, but I've not found anything really clear.
Any heroe can help us? Maybe we just need to change something in "about:config"?
Regards
I was desperate about the same Problem and didn't find any solution although many people seemed to have the same problem.
I solved it by calling
webDriver.switchTo().defaultContent();
before calling any findElement method
(using Java)
This error generally comes when you do no switch back from frame and trying to access web elements directly.
Use driver.switchTo().defaultContent(); and then try to access the elements
I finally made a "cheat" to the browser.
I got the fail when Selenium clicked on a link and try to open the new page. What I've made is just simulate the click, doing a selenium.open("URL") which replace selenium.click("link=ButtonWhichOpenTheURL").
It seems to work by the moment
I am facing the same error on Firefox 23 while reopening a pop up browser window. The only workaround I did is closing the current selenium session and relaunching it again. It worked fine for me.

VS2008 won't show Trace output

I'm using Visual Studio 2008. The Trace output is no longer being shown in the Immediate Window any of my forms except the primary form. When it executes code from within another form (called from that primary form) the Trace output doesn't show up. It used to be fine, and one day it just stopped working. I think this is a setting in VS2008. Anyone have any idea what setting this would be under?
It's got a TraceListener in the code, and that hasn't been touched.
Can you do a quick check and see if the second project is compiling in Release or Debug? If it's Release there's a chance Trace won't be defined and Trace output hence won't show up.
Check that you're referencing System.Diagnostics.Trace, and not the Page.Trace TraceContext object. If you're just doing Trace.Write it might be resolving to the wrong place, depending on your using directives.
There's an item under Options - Debugging - General: "Redirect all Output Window text to the Immediate Window". That should do the trick.
Patrick

VB6 lost F1 help function after Install of VS2005, re-install of MSDN2001 did not work

After installing VS2005 VB6 lost F1 function to MSDN Oct/2001 lib.
Suggestions to re-install MSDN did not work.
The only thing F1 works on now are ADO statements in VB6. Example ado1.recordset.recordcount If I highlight recordcount and press F1 I do get the ADO help information. If I highlight "recordset", I get "Help not found" dialog.
Same with say any regular VB tools property. lblEvent.Caption Get error trying to find help on say caption. If I highlight say Next in a for next loop I get a dialog that wants to know ... Multiple instances of the selected word have been found. Please select a topic and press Help. In this case VBA is one, Excel is one MSComctlLib is one. If I highlight FOR in a statement I get the "Help Not Found" error again.
This happened to me once. The only thing I could do to fix it was a complete re-install of VB6 (wasn't caused by installing VS2005, but installing a component that added its own doc to Help). Probably not what you want to hear.
This happened to me after a Windows Update, or maybe it was one of the XP service packs. Un-installing hotfix 896358 solved my problem.
Something similar happened to me, trying to compile a vb6 dll wasn't working.
Turns out that an update had been installed in the background and i needed to reboot before it would allow me to compile it again.

Resources