GREAT news !!!

Thanks for the continued support for OS4!

Perfect!

Thanks!

Thanks looks like a great update.

Thank you. No more freeze when resizing the search window during a search :) Regarding new AISS menu, I posted a question/request on your forum http://codebench.co.uk/forums/viewtopic.php?f=14&t=59 Thanks again !

Oh thank you thank you THANK YOU! Donation time?

Crashes trying to load up an old project, crashes creating a new project, sticking with the older version for now.

@Caras
Quote:
Crashed for me also when loading an old project, and the crash was apparently due to the project dictionary format having changed. After ignoring the DSI and rebuilding the dictionary, all now works fine. I can create new projects with no problem.

@Rigo
My only gripe so far is that the Application Library registration still hangs after quitting the program (I reported this problem about a year ago). In fact, the way CodeBench handles registration needs to be revisited:

1) not only the app registration never goes away, but
2) the program doesn't implement the bare minimum as per this specification
3) CodeBench registers as non-unique (i.e. allowing multiple instances) but doesn't behave as such in Application Library terms. If REGAPP_UniqueApplication is FALSE, each new instance should perform its own registration (and receive a dedicated AppID) so that external control through a program like Exchanger or AppManager can be applied to a particular instance. Instead, CodeBench allows multiple instances on a single registration, which leaves APPLIBMT_ messages with no specific target to arrive at (and currently ignored by the program).

It appears CodeBench performs registration when its codebench.library starts up, and unregisters when the library is expunged. Which unfortunately is not the case: after quitting all instances the library is still present in the system (I've checked with SysMon). This explains why the registration hangs.

My advice is: remove the registration code from the library, and put it where the actual program starts. In your event loop implement support for Application Library messages, namely: APPLIBMT_Quit, APPLIBMT_ToFront, APPLIBMT_Hide and APPLIBMT_Unhide.

Otherwise, there's no point in registering at all. Currently the registration is purely formal as CodeBench does not make use of any Application Library features.

@trixie Hmm, I was sure this issue was fixed shortly after you mentioned it. It needs to register in order to issue notifications, but looking at the code, it registers, sends the notification, then unregisters, so it is difficult to understand why it's hanging around afterwards. What program are you using to see if the registration is still valid? The notifications are sent via a separate process, this is why it is done in the library. It was tried all sorts of different ways and trying to do it synchronously led to all manner of problems, including lock-ups. Simon

@Rigo

Quote:
Exchanger, AppManager and SysMon - they all report CodeBench still being registered after it quits.

My (other) problem is that system utilities now exist that keep track of registered applications and allow controlling them via Application Library messages. On top of these, I'm now developing a program switcher commodity that allows flipping between running applications, sending them an APPLIBMT_ToFront whenever the user wants them to become the active program (much like you do with Alt-Tab on Windows). The trouble is that if Application Library support is implemented carelessly or is incomplete, the APPLIBMT_ messages don't work and it is the control utility that appears broken. And the user will get annoyed that the selected program won't come to front despite being told to. This is why I'm trying to advocate that the Application Library support be implemented according to the Wiki spec. It's not to hassle programmers but to enhance user experience and improve program control in the OS.

Well, like I said, as there is currently nothing in the OS that will manipulate applications the way you suggest, even if we wanted to try and incorporate something like this, there's no way it could be tested. Unless you want to send over your program, of course... Simon

"there's no way it could be tested" SysMon allows to send all type of Application messages (even custom messages) to any registered Applications. Sorry for the off-topic...

@zzd10h Isn't that only available via AmiStore?

yes, it is

@Rigo

Quote:
This is not about me suggesting something The program control/messaging facility is part of the Application Library, which has been a component of AmigaOS4 for more than a decade. The APPLIBMT_ control messages are meant to be sent to running registered applications, as per the official documentation. Why no-one made any practical use of it for so long is rather a question for the OS dev team: the system has Exchange (a program for external control of commodities) but none for registered applications.

Vicente Gimeno developed AppManager in 2010 to control programs in a way similar to Exchange. It can also be used for testing whether your APPLIBMT_ message handling is implemented in a correct and safe way. The program is freeware.

Guillaume Boesel's SysMon, too, can send the entire APPLIBMT_ message range to running applications. The program is part of the zTools package, available from AmiStore for peanuts.

I have developed Exchanger as a crossbreed between Exchange and AppManager. It allows controlling both types of program from a single interface. The program is part of the Enhancer Software suite.

Now it's asking for a Code: volume, then it deletes the SDL2_main.lib. I'm done.

@Caras

What are you actually trying to load into CodeBench? If it's an existing project does it reference the CODE: volume ?

@trixie Well, I assume you'll be happy to hear I have managed to rejig the application.library code, and now have supported all the features supplied by Appmanager. Hopefully, that'll keep you happy :) Simon

@Rigo

Call me a man of simple pleasures but you've really made my day! Thank you!

One caveat though. Please make sure that your handling of the APPLIBMT_ToFront message accounts for the case when the program is iconified. I've seen far too many times that programmers do



which of course results in a crash when the program window is iconified. Unlike IDCMP, Application Library messages are not window-centric and can arrive regardless of program state.

Don't worry, already tested under all perceivable conditions :) Simon

The Code: reference seems to just be because I had libpthread.a before the SDL2 libs. Not sure why any files were deleted. I've reverted back to a previous version of codebench anyway.

Rigo,

thanks so much for this update! However, it seems that in the archive there is an AutoInstall file but AmiUpdate doesn't update anything. And in the AmiUpdate Database there seems to be no entry for Codebench. Could you update the database, please?

Marko

I've also noticed that the RichEditor Gadget has become much more sluggish with this release. On my Sam440ep-Flex, key presses often get eaten unless I type really slow. This is a nuisance, as I always have to move the cursor back and insert the missing characters :-(