This window appear all the time when I change Delphi's tab 'Code' to 'Design'. How can I fix this problem?
I've encountered this exact issue before using Delphi XE8. I found no solution other than restarting the IDE when it happens.
In particular, this happened whenever I would switch between Local Desktop and Remote Desktop. For example, I would start the IDE from locally at the computer itself. Then, I would go to another computer, and open Windows Remote Desktop to that computer, into the same desktop session, and when I went to use the IDE, it would give me the same Invalid ImageList Index error repeatedly.
Since then, I've been using Delphi 10 Seattle, as well as not using Remote Desktop. So I can't say whether this has been fixed yet in later Delphi versions. But if I recall, past attempts to use Delphi 10 Seattle via Remote Desktop have been successful.
i think i found the problem.
if look carefully on the error details.
the firs row show calling delete on custom image list...
so i find out if i delete FMX.ListBox from uses, it will solve my problem.
and it worked. so i think the problem is a bug on Firemonkey ListBox unit.
I Solved with a simple Alt+F12
Related
With XE8 update 1, Win 7 64 bit and a single component added to an otherwise empty folder I get:
error: [dcc32 Fatal Error] F2039 could not create output file .\Win32\Debug\MountTest.
The test will compile and run fine the first time but XE8 has to be shut down and restarted to compile again. The component is a gauge from Mitov Software.
The component vendor say's that this is a known bug with no fix. If so its a showstopper and project end'r for me. Is it really the end of the line for Delphi?
I hope some one can pull this rabbit out of a hat somehow.
This is what I have done to isolate the problem.
Started with a failing application (will not compile a 2ed time)
Remove all external units used
Remove al references to those units
Remove all references in the 'Uses' clause
Comment code until it compiles
It should compile every time you hit run (no problem).Now add a blank form to the project. Don't do anything to the form just add it. Add it to your uses clause.
Its should compile every time you hit Run.
Now open the blank form and simply touch it so that it needs to be recompiled.
When you run the application its back to failing when you run it a second time.
Notice that happens when you simply add a form and 'touch' it. No code needed.
This problem is not something wrong with my code - it can't be. Its a bug in the UI - must be.
Coincidentally, I just fought with this issue yesterday testing some components I ported to XE8. The output file in my case is the project executable.
After spending several hours trying to figure out what was going on (including efforts to reconfigure my AV software, disabling it entirely, moving the project to a different location, etc.), I was able to solve the problem by disabling Castalia. If I run the IDE without Castalia, the problem does not occur. If I enable Castalia again, it starts happening again.
You can find instructions for disabling/enabling Castalia in How can I disable Castalia in XE8?
I'm removing the above content because the issue has reappeared (with Castalia disabled). Further investigation shows a couple of things:
The problem seems to be related to any sort of exception being raised in the debugger (even those that are handled in the code). Clicking either Break or Continue in the debugger exception dialog works as always. However, the next attempt to compile or build the application fails with the F2039 error. Deleting the executable in Windows Explorer allows compilation and running once, and then the error recurs.
Restarting the IDE fixes the issue, until the next debugger exception occurs.
Neither taskkill or a batch file with del worked in either a pre- or post-build event.
There is an open QC entry for it at Embarcadero which indicates that it was reported in XE7, XE7.1, and XE8, and is currently an open internal ticket. I can't find a way to add the information in the two points above to that open ticket in the new JIRA-based Quality Portal. Perhaps someone who has access and can do so will on my behalf (or at least add a link to this post).
It's not linked to a specific project. The original answer (as mentioned above) was related to a test app while porting some components to XE8 from an earlier version. When the problem reappeared for me, it was in a brand new project, totally unrelated, that does not use any non-standard components.
(I previously had access to EMBT QC, and had a few open tickets. The accounts appear to have not migrated to the new QP, and I can't locate any tickets there under my account.)
Found It.
I decided to start from scratch on my development system and uncovered the problem.
I installed Windows 10 on a virgin disk
Installed XE8 update 1
Installed MITIOV Instruments for XE 8 and tested them. All working find
Installed AsyncPro - Still working
Installed the JEDI Jcl - Fails
Remove JEDI Jcl - now works
Trash JEDI completly - Everything works fine
Something in the JEDI Jcl version 3.48 is causing the problem. I can code around the JEDI components I was using without to much trouble but its a shame.
How about automatically kill your "hang-up" application before build?
I also had this problem on Win 7 Pro 64 bit with XE8.
Removing JCL fixed the problem. If I was a betting man, I would look closer at the JCL Debug IDE extension.
Guy's..
There is no reason to upgrade to Delphi 10.1, because all previous versions are equipped with an older version of the Android SDK.
Now, how to solve this annoying issue:
Just find the map where the Android SDK is located.
See: Tools/Options/Delphi Options/SDK Manager/Android Location
Now run the ..\sdk\tools\android.bat as Admin
This will show the Andoid SDK Manager.
Next is to update to the newest Android SDK and SDK Tools.
If all completed, you don't have to upgrade to Delphi 10.1 or whatever "advised".
Restart Delphi and problem:= solved!
btw:
It took some effort to find out what's happening here, because the Eclipse compiler suffered the same issue as Delphi. Finally all was related to bugs in earlier versions of the Android SDK causing adb.exe to keep a filehandle held hostage.
I have developed an app for computers a while back, that generates a word document and saves it automatically under a name provided by the software.
The application has worked perfectly in windows xp and windows 7. But now it needed to be moved to a windows 8.1 computer and since the generating works perfectly. But the save command wrdDoc.SaveAs(SaveToFile); does not work.
Basically what happens, is on that command's execution a save dialog appears and you can save the document yourself. After you click save. You get an error command failed with no further details.
Is there anything that has changed since windows 7 that prevents this code from executing properly?
The old computer used the following:
windows 7
office 2007/2010/2013(all were used at some point in time)
New computer:
windows 8.1
office 2010
UPDATE:
it is also worth noting, the dialog does not show any of the word documents in the folder if i browse there... Can this be a hint to the problem?
Resolved
I managed to find the problem. It's a brand new laptop, and Acer had a bunch of crap installed that sync's with office and explore. Once i uninstalled that the software returned to working normally...
Thank you guys anyway so much :)
It depends on your word version. Only 2007 has a "Saveas" method for the document object (https://msdn.microsoft.com/en-us/library/bb221597%28v=office.12%29.aspx). The later versions (2010 and 2013) only have a "Saveas2" Method (https://msdn.microsoft.com/en-us/library/ff836084.aspx)
Delphi 7 has been running fine for a long time (months on this machine, many years on others.)
However, although I know of nothing that I changed (and certainly didn't install any components) if I try to run a newly created, simple program, with one form, while I'm in the IDE, I get an Access Violation at address 006DDDC2 in coreide70.bpl.
The program runs fine outside the IDE.
I'm running no add-ins (like Delphi Speedup...)
Other than completely ripping and re-installing, any suggestions?
A rip and re-install solved the problem ... for a while, and then it re-surfaced.
For anyone having the same problem, I have traced this down to something being corrupted in my saved desktops. Since the problem was occurring when I tried to run a program, it would naturally switch to the debug desktop. Apparently it was corrupted. Saving a new desktop to replace the old desktop resolved the problem.
The first thing to try is to remove packages from the IDE. Try this out with your vanilla empty app rather than your real app. If that doesn't help I'd move straight to a Delphi reinstall. That really ought to fix it and there's probably nothing to be gained trying to solve the problem with a reinstall.
After upgrading to Windows 7 all seems to work in my Delphi 2007 version except this one.
I know that 2007 is not build for win 7 but I'm not sure that the OS is the reason. My friend is using it without a problem.
When I use "Find Local References" all is fine.
Do you know a fix for this? Some dll registration may be?
I found the solution!
When I used Refactor -> Rename menu delphi didn't blew up but kindly show me the error. Unavailable interface call with the name of it.
So after short research I've registered 2 tlb files and all is working now.
..CodeGear\RAD Studio\5.0\bin\Borland.Studio.ToolsAPI.tlb
..CodeGear\RAD Studio\5.0\bin\Borland.Studio.Interop.tlb
I used tregsvr.exe for the registration without a problem under my x64 system.
P.S. I still wonder what else is not registered during the installation .. hopefully all is good.
We have a few different programs all compiled together in the same suite, recently we had a bug reported that "The Right Click Shortcut Menu was missing."
So as with any bug I tried to reproduce it and couldn't. No matter what I did the right click menu appeared on my system.
My first guess was that this was an OS issue. We know it works on Vista and XP, but on Windows 7 it doesn't. Unfortunately this issue only affects one of the programs in the suite and seemingly only on this one machine. AFAIK there isn't any code we've written to allow or prevent the default menu appearing so I'm not sure why it only affects one program.
The machine with the issue is a 32-bit machine running Windows 7. There was another issue to do with the regional settings (we have noticed backwards date formats even though the OS thinks it's UK it had been displaying MM/DD/YYYY format, but this was fixed when changing the regional settings to something else and back again). This did not resolve the issue.
Besides writing a new context pop-up, does anyone have any idea how I would even start to diagnose this issue? Is there an API I can call to pop-up the default menu so I can monitor its behaviour? some windows message I can intercept the check its all running as it should be?
Download Delphi 2007 December updates to fix this problem
or andy Context menu popup delay bug fix unit