Though you could start by just opening an image specified in the icon tooltypes. "SPLASHIMAGE=splash.png". And center it on the screen using a borderless window.
I have been wondering why OWB does not have some sort of splash window to let you know you have actually clicked its icon. I was going to suggest it but I don't need to now !
The delay before any user response is given is far too Windows like. Nothing seems to haoppen for ages before the main window opens.
Opening a small centered window is not too difficult is it - sort of the next level in any Amiga C tutorial from the "Hello World" example
Another request, could OWB be made to open its own screen rather than going via the rather hacky way of setting up a screen entry in the Screens prefs. The latter is a much slower way of doing theings than the normal Amiga way.
Another request, could OWB be made to open its own screen rather than going via the rather hacky way of setting up a screen entry in the Screens prefs. The latter is a much slower way of doing theings than the normal Amiga way.
I have a suggestion to everyone. Open any text editor like Notepad f.ex. Type the following lines but replace all file names and their paths with correct ones. You don't have to write comment lines which start with ";":
; This will open your splash window Run >nil: Multiview MyDataPartition:MyPictures/MyPreferredSplashPic.pic PORTNAME SPLASH ; Wait 1 sec so starting OWB doens't slow down opening the splash window Wait 1 sec ; Start OWB with WBRun command so OWB can find its tooltypes WBRun Internet:OWB/OWB ; Wait for the OWB.1 message port to appear so we will know it's running WaitForPort OWB.1 ; Close the splash window rx 'address SPLASH QUIT
Enable "Create icons" from Notepad's settings menu and save that script you just wrote. Make that icon executable (possible to run). Then use that icon (script) to launch OWB from now.
Rock lobster bit me - so I'm here forever X1000 + AmigaOS 4.1 FE "Anyone can build a fast CPU. The trick is to build a fast system." - Seymour Cray
I have the launching code itself done already. I just need to add some code for opening/closing the window and reading the tooltypes. This should be relatively so I'll probably get it finished tomorrow already.
Cool If only multiview had an option to remove window title...
"the expression, 'atonal music,' is most unfortunate--it is on a par with calling flying 'the art of not falling,' or swimming 'the art of not drowning.'. A. Schoenberg
nobody tried the source and exe i pointed before? it has already what you need.
I tried it, and ran it from ram:, but once the eye picture loaded my whole system locked up. I presume it has to be in the OWB directory?, but I haven't sorted it out yet.
I have it working now. Now I just need to write a .readme file and upload it.
I had originally intended to just use NP_EntryCode to signal my program when OWB has been run but it seems there is a long time between this and the OWB window opening and very little time (a fraction of a second) between SystemTags() and the EntryCode function being run so I've added a WAITFORPORT functionality for waiting for OWB's public message port. It's written to work even when running several instances of OWB and is working quite nicely in the tests I've done here.