See intuition.library/StartScreenNotifyTagList. Read the autodocs for more information.

For OS 3.x check screennotify.library: http://aminet.net/package/util/libs/ScreenNotify10

This sounds like being a coder is a disease and coders need to be put under quarantine.

Why do you think that coders need to hide from or be protected against other users?

A public sub-forum would be completely suitable IMHO.

When a device replies to an IORequest, the ln_Type field is set to NT_REPLYMSG. When WaitIO finds ln_Type to be NT_REPLYMSG, it does not wait but simply removes the message from the port. So it is safe to call WaitIO if the message has already been replied. Of course you must make sure that your interrupt only fires for the IORequest you want to receive.

Do not run YAM directly but put a script like this in either drawer and run it instead:

Here are some examples how to play sounds with datatypes:

http://thomas-rapp.homepage.t-online.de/examples/dtplay.c
http://thomas-rapp.homepage.t-online.de/examples/playpoly.c
http://thomas-rapp.homepage.t-online.de/examples/melody.c

STM_ are methods. You need to look for attributes which are called STA_.

System-friendly double buffering: http://thomas-rapp.homepage.t-online.de/examples/dbuf.c

TBImages are there: http://www.masonicons.info/6.html

@MickJT

We only see that he runs Ed several times, we don't know what he does with the editor window once it is open. If the editor remains open, Ed will use the copy in memory and send a new file to it. And even if the editor window is closed, ced remains in memory if you don't end it with "Quit & die" from the menu. Appdir is another possibility.


@JosDuchIt

Seems like something has screwed up your path. Without being able to examine your system it's difficult to tell how. One possbile reason I could imagine is that the path change is not done in the startup CLI.

You need to know that the path is a local thing. Each CLI process has its own path. Using the Path command only changes the path of the CLI process it was executed in.

A child process inherits the path from its parent. So if you change the path in one Shell window and then enter NewShell into this window, the new window will have the same path as its parent.

Knowing this, the only way to have a "global" path is to set it in the initial CLI process because all other processes are created from this one.

Now, for example if for some reason you changed the section in startup-sequence from execute s:user-startup to run execute s:user-startup, all path settings done in s:user-startup only affect the child process created by run and are thrown away when user-startup ends.

Similarly if you run scripts from WBStartup which try to change the path, then these changes only affect the commands which follow in the script and are thrown away when the script ends.

Is there any reason why you always do this in the S directory?

Do you have a file called CED somewhere else in your DOS path, perhaps a script file?

Enter which CED to find out.

You made an assign CED: which points to Datas:Teksten/CygnusEd. Now you run CED:Ed which is equivalent to Datas:Teksten/CygnusEd/Ed. This Ed program tries to run a program called ced. The ced program is stored in Datas:Teksten/CygnusEd, too, but because Datas:Teksten/CygnusEd is neither the current directory nor belongs to the DOS path, it cannot be found.

After you change the current directory to Datas:Teksten/CygnusEd, Ed can find ced successfully.

The "ced: unknown command" message does not refer to your CED: assign. The ':' is part of the message. It says "command: unkown command" where command is ced.

You need to add Datas:Teksten/CygnusEd to the DOS path if you want Ed to always find ced.

Try

delete ${test}/file.txt

Edit: better ${test}file.txt

Your code resolves to ram:/file.txt which is not correct. The right path should be ram:file.txt.

Edit2: os4 contains some new shell commands which allow to connect and split file name components. I don't remember the names, but as they refer to the similar dos.library functions, they supposedly are addpart, filepart and pathpart.

Knowing that, your delete would probably be best like this:

set testfile `addpart $test file.txt`
delete $testfile

or

delete `addpart $test file.txt`

This example does not have a sizing gadget. Actually I never put a sizing gadget into a window when working with GadTools. I layout the gadgets and calculate the needed space and then open the window with fixed size.

The problem with GadTools is that existing gadgets cannot be changed after they were created. So in order to change the window size you have do destroy and recreate the entire GUI.

To reduce flickering when resizing the window one could remove all gadgets from it on a IDCMP_SIZEVERIFY message.

Why don't you convert your programs from GadTools to ReAction? ReAction does all layouting automatically. That's much easier to program.

Quote:

This example was developed with Dice C long ago and it has cos with double floats and fcos with single floats.


Quote:

They won't work if you don't initialise the AreaInfo in addition to the TmpRas.

You can use AreaMove / AreaDraw / AreaEnd to fill a random area.

Here is an example: http://thomas-rapp.homepage.t-online.de/examples/piechart.c

Quote:

It's the window's rastport. But all rastports share the screen's bitmap.

And as you might have seen in my source code, you should use AllocRaster instead of AllocVec(...,MEMF_CHIP). This is because RTG systems might allow to allocate raster data in FAST mem and CHIP mem is rare.

Well, I tested it on OS 4 and you are right, it does not work, not matter what I do.

I changed your code like so:



It works well on WinUAE in 3.1 and 3.9 with or without Picasso96. But on OS4 I get corrupted graphics. It does *something* but no flood fill.

Your TmpRas buffer is too small.

From the autodocs:

Quote:


The bitmap used in the RastPort is that of the screen, no matter how small the window is.

Use

If a directory is still locked after a reboot, there is a simple trick: rename it to "delete_me" or similar and then reboot again. After that you should be able to delete it.