corneliusdavid

Well, you could put the code you want collapsed in a {$REGION} because regions are collapsible. But that's a lot of extra work--and more lines of code.

I'm using the scButton from StyleControls to pop up a secondary form right next to the button--and it works well. When there are multiple scButtons, I'd like a click on a different button to immediately close an existing form and open the other one just clicked; instead, the first click closes the current form and I have to click again to open the next form--requiring a double-click on the button to open the next form. For example, in the DropDown Forms demo that comes with StyleControls, if I click one of the drop-downs that open up a mini form showing a list of selectable items but before choosing one, click on "scButton2", I don't want to have the first click close the list form and then have to click scButton2 again in order to open its form, I just want to click once and the list will close and the new form immediately pops open. In other words, I want one click on scButton2 to go from here: to here: How do I close the first pop-up form and open the second in one click?

This has been fixed in today's patch ... https://blogs.embarcadero.com/rad-studio-11-alexandria-november-patch-available/ Now, I can resume iOS development--and will remember not to upgrade quite so quickly in the future!

It takes some time to play around with it and get familiar with resources and suffixes. We could start a new topic to discuss this if you want.

Thanks for your comments--so glad it was useful!

Well, yes, I was surprised how many of those comments came through. In my recollection, most of those were near the beginning of the session. But consider this, too: responding with a quick smiley-face or one word response (e.g. "Agree!") takes far less time and effort than doing research on a question you may not know for sure. People take what is said in these sessions as gospel so the answerer needs to be certain what they're saying is spot-on.

I think they were fielding questions as fast as they could but could only get to so many. It went over time as it was. I've been on that side of the screen and you just can't get to everyone's question or comment.

The REST Debugger is definitely convenient--especially with the Copy Components button--but it is buggy and sometimes I have to restart that as well. I use bookmark stacks and the code mini map far more often, and in more projects, than the REST Debugger. Getting those back in the next month would make a nice Christmas present!

I guess I just have seen so many negative comments on these forums and I just had seen one too many. The Embarcadero of today is a long way from the Borland of yesterday; today's companies seem much more focused on profits than community. I remember the CompuServe days, the flame wars on newsgroups, and being able to connect directly with TeamB. Perhaps this is the last place to collectively vent. Still, it seems that comments are too often directed at programmers that don't likely have much control over their priority list. We can only hope that our frustration is heard up the chain of command. The Bookmarks and Navigator plugins are my favorite additions to Delphi--I've blogged about it recently. I too am waiting and hoping for an update.

It never ceases to amaze me how people in these forums can have such deep and intimate knowledge of the code of the IDE and it's plugins and libraries that they feel they have the right to highly criticize the hard-working team behind the complex and powerful development tools we use. As an independent programmer, I can set my own deadlines--and I don't release anything until I'm sure it's ready. When I worked for a large corporation, executives that have to please shareholders are the ones that set deadlines--and whatever code was ready, was released. I'm sure the Delphi team would've loved to postpone the release of D11 until it was more fully tested and all the plugins were finished to be released along with them but I'm also fairly certain they didn't have a choice and are also not allowed to voice those internal issues. Personally, I feel sorry for them and the pressure they must be under, especially when they read these posts and can't do a single thing about it.

I've tried that. I removed the iOS platform from Delphi, deleted the folders, did a total clean of the project (and also tried a brand new project), re-added the platform which re-added the SDK folders... Still got same linker error. So this is a problem with Monterey? Doesn't Delphi import the libraries and frameworks from Xcode? I can build a bare-bones Xcode project on Monterey to my iPhone.

I have the following: Delphi 11 on Windows 10 and Windows 11 Mac Mini with macOS Monterey 12.0.1 on a 3 GHz Intel Core i5 Platform Assistant Server vr. 13.0.12.0 iPad and iPhone both running iOS 15.1 I've had problems in the linker process trying to get even the simplest bare-bones app to build for iOS. I have no problem with Android or MacOS--it's just iOS. At first, I had an error finding the /System/Library/PrivateFrameworks directory. Looking through the SDK Manager for iPhoneOS 15.0, I found a the Remote Path with that entry and removed it--since it didn't exist on the mace where I found other framework folders. Now I get the following error: [DCC Error] E2597 ld: file not found: /System/Library/PrivateFrameworks/DocumentManager.framework/DocumentManager for architecture arm64 I cannot figure out why it tries to link that file and why, if it expects it, that directory does not exist on the Mac--like I mentioned, other "framework" folders exist. I've removed and re-added the iOS platform looked through the .dproj, and refreshed cached SDK files. I've got this problem on two different computers and have run out of ideas--and patience. Anyone have any suggestions?

I decided to move up to Delphi 11 and just use their default platform installer for Android. I also decided to retire the old Android ZTE phone. I'm able to compile, debug, and run both Android and iOS apps from Delphi 11 now. I was still getting the weird error listed in my previous post for the DelphiVersions project though, even after deleting all temporary files and recompiling. Finally, I just renamed the project to DelphiVersionsMobileBroken, created a new blank mobile app, added the forms, removed the default form, set up the icons and version info--and it works! Something was seriously amiss--but everything is back working now--and in Delphi 11. Whew!

Back to the DelphiVersions project, I deleted all temporary files, even including the .dproj, .deployproj, and .res files and opened the project back up, reset some simple version info and rebuilt (still using Delphi 10.4). Now, it's not even getting to the deploy stage because it can't finish building the package, giving me this error: "Resource package cannot be an empty string (at 'src' with value '@drawable/splash_image')" and references the file, splash_image_def.xml. But looking more carefully at Delphi build output, I think one of the SDK tools is configured incorrectly: [PAClient Error] Error: E2312 Unable to execute '"C:\Users\Public\Documents\Embarcadero\Studio\AndroidSDK\build-tools\30.0.3\aapt.exe" package -f -M "V:\DelphiVersions\104Sydney\DelphiVersionsMobile\AndroidManifest.xml" -F "V:\DelphiVersions\104Sydney\DelphiVersionsMobile\bin\DelphiVersionsMobile-unsigned.apk" -I "C:\Users\Public\Documents\Embarcadero\Studio\AndroidSDK\platforms\android-30\android.jar" -S "V:\DelphiVersions\104Sydney\DelphiVersionsMobile\res" -A "V:\DelphiVersions\104Sydney\DelphiVersionsMobile\assets" "V:\DelphiVersions\104Sydney\DelphiVersionsMobile\library" "V:\DelphiVersions\104Sydney\DelphiVersionsMobile\classes"' (Error 1) Maybe I should reinstall Delphi 10.4's Android development.

I was testing on an old ZTE with Android 7.1.1. I switched over to my Google Pixel with Android 11 and can debug just fine now--thanks!