In my aplication I open an InternalWindow with menu/item. When the modal window should be closed with close() the whole application exits. It seems that this behavior is present since version 1.7.15.
Greetings from Germany.
This bug was fixed a little while ago and is available in the SNAPSHOT releases. It will be in the 1.7.16 release shortly :)
Related
This question already has answers here:
Delphi XE3 and higher not saving open IDE tabs on exit
(2 answers)
Closed 3 months ago.
I searched Stack Overflow and found my question... but it's over 10 years old and Delphi has changed so much since then.
This: Delphi XE3 not saving open IDE tabs on exit Is not valid for Delphi 11.0.
I'm running Windows 10 and using Delphi 11.0
I want to be able to go back to any project with all the TABS I had left open when I closed the project, but Delphi always starts with the project TAB only and sometimes doesn't start with any TAB at all!
I searched and found my question on Stack Overflow, but the answer has changed, because Delphi 11 no longer has Environment options or the methods described in the answer. All things have must have moved or no longer exist??
Your help is very welcomed!
Okay, after digging this is what I found: https://docwiki.embarcadero.com/RADStudio/Alexandria/en/Saving_and_Recovering
For Delphi 11.0 make sure this is checked:
Tools > Options > IDE > Saving and Desktop > Save project desktop when closing
What bothers me most is that the documentation on Embarcadero just seems to be copied over to the next version without much thought.
I found this: https://docwiki.embarcadero.com/RADStudio/Alexandria/en/Environment_Options and if you try to do Tools > Options > Environment Options ... YOU WON'T FIND IT!!! ... it's in the documentation, but it doesn't exist!
I hope this saves someone time and money!
I'm on Xcode 13 GM (13A233) and I'm noticing that it won't stay paused when it hits a breakpoint. It stops, but about a minute later it just resumes. Is there a new default setting that might cause this? I don't see anything relevant in "Behaviors," but maybe I'm missing something. Has anybody else encountered this issue?
The only unusual thing about my project is that I am calling Python from it, using PythonKit. But this breakpoint pause issue isn't isolated to code involving PythonKit.
I've tried all the usual "fixes"—i.e., clean build, delete derived data, reboot, etc. The app is just a simple SwiftUI app for macOS.
This is actually the debugger crashing and the app detaching: The LLDB RPC server has crashed. You may need to manually terminate your process. The crash log is located in ~/Library/Logs/DiagnosticReports and has a prefix 'lldb-rpc-server'. Please file a bug and attach the most recent crash log....
It doesn't do it my main View, but does do it in a static method called on a singleton in the app, and also at various points in a custom package I'm developing alongside the app.
I see a similar unresolved issue from August at bugs.swift.org: https://bugs.swift.org/browse/SR-15110?jql=text%20~%20%22lldb%20crash%22, In case anyone else is seeing the same issue (maybe you can post your log there).
UPDATE: I completely forgot that I was running on a dev snapshot toolchain. All good in Xcode 13.1 with bundled toolchain. Moral of the story; if something really strange is going on, check your toolchain.
Not a programming problem per se, but rather a programming environment problem that I have been unable to find a solution to.
The problem relates to Adobe's Extendscript Toolkit (both 3.5 and 4), but so far I haven't been able to solve the problem, so here I am...
The error I get has appeared more or less over night. I didn't experience this problem yesterday, nor this morning. But exactly WHAT has happened is beyond me. I have removed preferences, I have uninstalled, reinstalled, created a new user, restored old preferences from Time Machine and I'm now pretty much lost for options.
Basically, nothing works in ESTK anymore. Just opening ESTK and entering alert('Hello') won't work. Neither will $.writeln(). Everything running from within ESTK seems to give the same error;
Cannot execute script in target engine 'main'
With details:
Cannot execute script in target engine 'main'!
(#1116) Can't start debug session.
Below is a screenshot taken from the new user I created to test, same problem.
The "funny" thing is that all the scripts (InDesign CS5, still hanging on to it for reasons) still work perfectly in the applications' script panels. So there is nothing wrong with the scripts (heck, they haven't changed one bit, and still refuses to run in ESTK).
As mentioned, I've tried installing the ESTK CC (version 4) as well, but the very same problem occurs there. Which leads me to think the problem lies somewhere else, but I do not know where, and why.
So, if anyone can shed any light on this issue, at all, I would be very happy. Debugging is basically the only thing ESTK is good for in my book, but now that even that functionality is gone, I don't know how to efficiently debug the scripts which is kind of hampering the workflow.
For reference, I'm running InDesign CS5 (from the old Creative Suite) on a 2008 Mac Pro with 10.11.6 (El Capitan) installed. Well aware that it's pretty out of date, but that is beside the point here.
In the above mentioned forum, Adobe has published a stable workaround!You just have to correct a setting inside the estk application:
Open the file(Mac): “/Applications/Adobe ExtendScript Toolkit CC/ExtendScript Toolkit.app/Contents/SharedSupport/Required/cdic/11BTBackend.jsx”
Search for the value: 604800000 (line reads bt.timeout = 604800000)
Replace that value with 604800 and save
Quit ExtendScript Toolkit and relaunch.
I can confirm that it works.
From the adobe Forum :
"we have found a first workaround: just change your date to any date before 20-nov-2018"
https://forums.adobe.com/message/10761440#10761440
Seems like a date issue :(
I just published a quick update about this on the Adobe Tech Blog.
For the time being, if you dismiss the dialog, you can still run your script via ESTK and step through code as usual.
Alternatively, if you really want to avoid the dialogs, and you don’t mind setting your clock back, you can sidestep the issue by setting your system clock back to November 19, 2018 or before. On most systems, changing the system time can have unintended side effects, so this isn’t recommended unless you’re really certain about it.
Every time I open the IDE it starts loading then shuts down before I get a chance to change anything. Remember this happening before on previous Versions of Xcode but I haven't had to deal with this in a rally long time. Any ideas?
PS. I think its Xcode 8.2.1 ,really hard to check when it closes down immediately.
Found that deleting Derived Data enabled X-code to start responding again.
Was difficult to find it though as most people were explaining how to find it from within Xcode :P If future me or any other super-devs would like to know the default directory then you can find it under the hidden folder Library on your user directory IE. /Library/Developer/Xcode/DerivedData/
Since installing XCode 6 GM, it has been freezing and locking, showing the spinning wheel of death while I attempt to edit code that has syntax errors. Has anyone else seen this, and are there any known work-arounds?
I foolishly abandoned my cautious strategy of saving the previous version (Beta 7) and it appears that Beta 7 is no longer available for download. Are there any known archives of / for the link?
I have also posted to the dev forums and will follow up with a bug report, but it is hard to pin down the exact circumstances.
Edit:
Additonal Notes:
CPU: SourceKit Service is generally around 100%, but that has seem to have been the norm for the flavors of XCode, and the CPU seems to properly drop off when it finishes recompiling.
RAM: SourceKit is no longer exhibiting the memory leaks that used to cause it to halt and catch fire, memory does not appear to be a factor, and there are several ~ 5+ gigs to spare.
Environment:
Late 2012 Mac Mini, 16GB RAM
OS X 10.9.4 (to be fair, this was new today as well, driven by the requirements of XCode 6 GM).
That said, only the software changed today.
Update
Apple claims that this bug is fixed in Beta 6.1, for what it's worth.
You should look if you have any imports missing in your bridging header file. Sometimes even commented out imports will cause this behaviour. For me it was commented out Pixate Freestyle Cocoa Pod. I had to remove pod completely from my project to stop SourceKitService from crashing.
https://stackoverflow.com/a/25173389/527539
I can't say any of these fixed the issue, but they alleviated the situation:
I removed all playgrounds from the project tree. Saved them somewhere else.
I removed all objectiveC code from the swift project (when possible). This Spinning-wheel, BTW, is a problem only in my swift projects. My other Objective-C-only projects are fine.
It looks like it's the background indexing process which is taking all the CPU. Open "Activity Monitor" and see it right there at the top, using 360% CPU. Lowering the priority for this process helped as well (type in terminal):
renice 10 -p [pid]
Make sure to take the correct process id from Activity Monitor.
The higher the number (should not exceed 19) the lower the priority.
I make significant changes one at a time. It seems that the amount of errors in the file affect how many times and for how long the spinning wheel spins. It looks like some type of errors trigger it more often than others, but I'm not able to pin point which exactly.
XCode had a similar indexing issue in previous versions (see this Xcode4 issue: How to disable indexing in Xcode 4?) which gives me the hope they will fix this issue sometime, hopefully soon...
I create a new tab via menu File->New Tab and close the old tab that is frozen.
CmdT does not work that time.