@djrikki

You can use "SmartButton" from OS4Depot to do exactly that (and much more)

@corto
An updated GCC may bring evolutions to the C and C++ standards that emerged since the release of GCC 4.4.x (e.g. c++11).

@broadblues

Yes you are right but I thought it was not recommanded to look at what nor how AppDir handler was storing its database. If it is publically accessible then yes AppDir variables can be used as a replacement of the AppPath.

@Rigo

Quote:

One advantage that AppPath has over AppDir is that being an environment variable it can be retrieved from the AutoInstall script this is really convenient both for the developer writing the autoinstall script and the user running it because he is not required to specify the previous installation path...
As a consequence all my software still have this "compliance" code. It really irritate me when I'm updating a software to be required to re-run the complete installation process including specifying the installation path: after all I'm updating not re-installing!

@zzd10h

I'll check again maybe something changed but it worked last time I checked it... Strange. I'll go on investigating.

@Phantom

X1kTemp has his own flaws for example if you constantly hide/show the dock where it lies it will crash. The only reported case was by one user in conjunction with AutoDock by Tuomas. But the crash is totally different as X1ktemp is clearly indicated as crashed.

For now on I can't produce the problem on my system, but looking at the crash log the bug is related to popupmenu.library and lies in AmiDock (not in X1ktemp.docky not in CPUDock).

@TSK

Are you using X1kTemp? Using X1kTemp at the same time as CPUDock does not cause any freeze, crash or whatever here. Be it on beta or public system.
The provided crash shows a crash in popupmenu.library which I don't explicitly use in my docky nor do I do anything to the context menu AmiDock provides to any loaded docky...

@LiveForIt

While having a bluetooth stack may be a good thing, I doubt a commercial company could find a viable business here. In fact if they concentrate on the AmigaOS4 market I doubt they can sell more than 200/300 copies at a price tag between 20 and 40 euros (40 being already expensive IMHO).
If they try to make a cross AmigaOS systems version (MOS, AROS AOS) they can maybe hardly reach the 500 copies.

Moreover this company has no (known) Amiga development background so either the bluetooth stack will be considered "alien" and will not match the standard Amiga APIs and GUI...

I bought the DVD at the Alchimie even if I'm not a gamer and will probably never use it, it's just a small amount of money to show support. I've done the same with MACE some weeks ago, and will do the same in the next weeks for Battle Squadron. IMHO it's the only way we can get much more quality productions for our platform: showing our support to the few remaining commercial developers.

@Cass

For me it works.
I choose a file without a real icon attached, DefIcons affected a default one and it is displayed ghosted, then I select "leave out" and the icon is displayed on the Workbench... with the same icon as when it was in its drawer.

It depends on the file system you used on it. The only tool still supported is PartitionWizard but it does not support every filesystem available.

*But* if your hard drive is making weird noises than it's probably because it's dying and no software tool will allow you to reliably repair it. The only advice I would give to you is to make a backup and buy a new one

Quote:

VVA (or TightVNC) will allow you to take control of a remote host running a VNC server. At most you will be able to share the clipboard (and only if it is plain text).
That's completely different to what SAMBA would allow to do: SAMBA will allow you to share some partitions and/or drawers will other computers. This enables you to copy/paste files from/to a remote computer to/from your Amiga.

That's two completely different kind of things. With VNC you take control of a remote host (i.e. with local keyboard and mouse you are controlling it and have a visual feedback as if you were in front of it). On the other hand SAMBA will allow you to copy/paste files.

Note that there are two alternatives:
- RDesktop if you are only planning to take control of Windows machines you might want to try it as it will be more responsive.
- Smbfs if you don't plan to share your Amiga's partitions but rather only connect onto already existing shares then it will be easier and faster to install Smbfs instead of a full featured Samba server.

@Antique

The kicklayout file does not contain so much things in it. Of course you'll a few seconds at cold boot. But at what price? You are just deactivating some system features, and obviously a few weeks, months away when you'll hook a new piece of hardware to your machine, you'll complain it does not works as others.
Moreover are you cold booting so much that a 5 seconds gain worth the trouble and hassle?

@vox
Quote:

You'll not save so much system resources because if the specific hardware is not detected by the kickstart module then it shuts down (and free its memory)

Quote:

See above answer. Adds to it that drivers in kicklayout have been carefully selected to ease booting and cut warm boot time as much as possible (anything loaded in kickstart at cold boot obviously does not have to be loaded from disk at each warm reboot). And finally there is already a driver management: if the dedicated hardware is not found the driver shutdown...

Quote:

"A good idea"?? IMHO it should be "programming rule"

Quote:

Yes you are perfectly right SWT is an Eclipse project, but more and more projects adopt it because instead of going full Java (like AWT and Swing) it's using the underlying OS gadgets facilities. Due to that it gains more speed and reactivity and as it's already available on all three major OSes people assume it's portable.

IMHO SWT is only required if one is developing a Desktop application that needs to compete with native applications user wise and with native look. And if you think AWT and Swing are huge tasks then SWT is way above that. That's because more aspects needs to be tied to the native libraries and it's almost certain that our current toolkits will miss some capabilities that we have to be emulated somehow (which in the end defeats the goal of using native components...)

Quote:

Where? I think you are mixing with something else. See below...

Quote:

The page you are linking to does not deal with KryoFlux software but rather to other piece of software SPS is making (ie its IPF library)

I din't have the impression the KryoFlux software was available, is it?

I started a port some time ago, and even got to the point it was working reliably. But as usual I got distracted by another project and the port never got updated (I wanted it to be updated to more up to date APIs and as such to take advantage of the new OS's features). I should probably release it "as is" but first I must finish with that temperature docky thing, then come back to the Wacom USB driver update I was working on before that, then release that ftpd update I'm sitting on for about one year and an half... and then eventualy resume that work on NetFS...

You should give more details.
The best is to upload your grim reaper onto crashlog.os4depot.net ( http://crashlog.os4depot.net/?functio ... graphics/edit/flphoto.lha )
For the assign you can assign it where you want, I'll probably remove the need for it in a further update.

PS: it's best if you create a new thread for flphoto related problems; now that flphoto has been accepted and is not in the upload queue anymore.

@samo79

I'll look at that, but first I'd like to finish the update of my USB Wacom Driver.