Who's Online |
55 user(s) are online ( 44 user(s) are browsing Forums)
Members: 0
Guests: 55
more...
|
|
|
|
Re: Rexx Script doc
|
Posted on: 2009/4/28 8:40
#201
|
Not too shy to talk
|
@unimon
The document Workbench-Arexx.doc is a description of the ARexx port of Workbench, not of the Rexx language.
Bye, Thomas
|
|
|
|
Re: GUI for Shell Utils ??
|
Posted on: 2009/4/27 9:43
#202
|
Not too shy to talk
|
|
|
|
|
Re: String gadget
|
Posted on: 2009/4/26 0:58
#203
|
Not too shy to talk
|
@Antique
Either you didn't #include <proto/intuition.h> or "gadgets" is not declared as struct Gadget ** or struct Gadget *[].
Also depending on what kind of gadget it is you should either use GadAttrs or GT_GetGadgetAttrs. Your method is only allowed if you use Kick 1.3 coding style, i.e. set up the struct Gadget yourself. In all other cases you should use the corresponding functions.
Bye, Thomas
|
|
|
|
Re: AmigaOne -- USB -- pc
|
Posted on: 2009/4/21 11:49
#204
|
Not too shy to talk
|
@Atheist
USB does not support to connect two hosts. All such cables are custom devices and need custom drivers on both ends.
Perhaps you can use two USB-serial adapters and a serial nullmodem cable. But that's probably slower than necessary.
To connect two computers which already have ethernet built in, ethernet is the best and fastest option.
Bye, Thomas
|
|
|
|
Re: how to save the Ram Disk icon position once for all
|
Posted on: 2009/4/13 15:05
#205
|
Not too shy to talk
|
@Kotler
I don't know of any risk. This method works since OS 3.9. I don't see a reason why they didn't make it standard long ago.
Bye, Thomas
|
|
|
|
Re: how to save the Ram Disk icon position once for all
|
Posted on: 2009/4/13 9:17
#206
|
Not too shy to talk
|
The ultimate solution is to add the following line to s:user-startup:
makelink RAM:Disk.info ENVARC:Sys/def_RAM.info soft
This makes the Ram Disk icon "snapshottable" like any other disk icon. You can move it around, snapshot it and it keeps its position without the need to copy something forth and back.
Bye, Thomas
|
|
|
|
Re: ASL is not my friend
|
Posted on: 2009/4/9 19:14
#207
|
Not too shy to talk
|
@orgin
There is nothing wrong with *this* code. You should post the complete program. Or at least a complete example which crashes, too.
Probably IAsl ist not initialized correctly. Or win does not contain a valid window pointer.
Bye, Thomas
|
|
|
|
Re: Check existence of assign
|
Posted on: 2009/3/22 13:34
#208
|
Not too shy to talk
|
@orgin
There is IDOS->FindDosEntry doing it easier.
@BillE
You can move -1 to pr_WindowPtr to avoid requesters.
Bye, Thomas
|
|
|
|
Re: Subscribing to file system notifications
|
Posted on: 2009/3/21 11:11
#209
|
Not too shy to talk
|
@orgin Why is it so difficult to read the *entire* description ?
If you requested that messages should be sent, via the
NRF_SEND_MESSAGE method, the MsgPort pointed to by the
NotifyRequest->nr_stuff.nr_Msg.nr_Port field will receive
a NotifyMessage. The following message fields are of
interest:
NotifyMessage->nm_Class
This is set to the value NOTIFY_CLASS.
NotifyMessage->nm_Code
This is set to the value NOTIFY_CODE.
NotifyMessage->nm_NReq
This points back to the NotifyRequest which caused
the NotifyMessage to be sent.
Note that you must return this message when you no longer need
it. Specifically, all NotifyMessages must be returned before you
can safely end the notification process by calling EndNotify().
And the include file (dos/notify.h) for additional information:
/* --- NotifyMessage Class ------------------------------------------------ */
#define NOTIFY_CLASS 0x40000000
/* --- NotifyMessage Codes ------------------------------------------------ */
#define NOTIFY_CODE 0x1234
/* Sent to the application if SEND_MESSAGE is specified. */
struct NotifyMessage
{
struct Message
nm_ExecMessage;
ULONG nm_Class;
UWORD nm_Code;
struct NotifyRequest *
nm_NReq; /* don't modify the request! */
ULONG nm_DoNotTouch; /* like it says! For use by handlers */
ULONG nm_DoNotTouch2; /* ditto */
};
You can get the user data from NotifyMessage->nm_NReq->nr_UserData. Bye, Thomas
|
|
|
|
Re: Subscribing to file system notifications
|
Posted on: 2009/3/21 8:30
#210
|
Not too shy to talk
|
|
|
|
|
Re: Is this a bug? FOpen()
|
Posted on: 2009/3/19 16:50
#211
|
Not too shy to talk
|
@afxgroup
FFS does not clear the E bit.
If you Open() a file with MODE_NEWFILE, FFS will set RWED and clear the file note. If something else is desired, this has to be done by the application. For example if EditPad should preserve the file note, it has to do so, not the file system.
Bye, Thomas
|
|
|
|
Re: Mapping the AMIGA key
|
Posted on: 2009/3/18 13:45
#212
|
Not too shy to talk
|
@Raziel Quote: Now my question, how have others solved this kind of problem? Look at the keyboard layout *before* you buy it perhaps ? I stumbled across a similar problem with a cheap Logitech keyboard, too: it does not have a Scroll key and thus cannot be used with KVM switches. No solution for that, had to stay with my old keyboard. Bye, Thomas
|
|
|
|
Re: LockDosList() troubles
|
Posted on: 2009/3/14 13:23
#213
|
Not too shy to talk
|
@orgin
Walk through the LDF_DEVICES list and check which device has the same dol_Task (or dol_Port) as your volume.
Bye, Thomas
|
|
|
|
Re: Lock() problem
|
Posted on: 2009/3/13 23:11
#214
|
Not too shy to talk
|
@orgin
A file which has just been created by Open or FOpen is exclusively locked and therfore cannot be accessed by anyone else. DirOpus and Workbench do not access the file but its parent directory. The directory entry has already been saved and can be accessed.
So if you Lock() the directory and read all entries with ExNext or ExAll or whatever OS 4 now offers, you'll see the file's properties.
Bye, Thomas
|
|
|
|
Re: C / Random Value
|
Posted on: 2009/3/9 23:04
#215
|
Not too shy to talk
|
@freddix Quote: For exemple, I want to get a random number between 0 - 640 ...
#define rnd(lo,hi) ((rand() % ((hi) - (lo) + 1)) + (lo))
Bye, Thomas
|
|
|
|
Re: iconmodule and fake icons
|
Posted on: 2009/3/3 18:07
#216
|
Not too shy to talk
|
There is already a hook mechanism for files without icons implemented in icon.library. DefIcons makes use of it. Other programs do, too, for example FxPaint. There is no need to patch anything. Although chaining multiple hooks might look like a patch, too.
Bye, Thomas
|
|
|
|
Re: GCC and boolean ....
|
Posted on: 2009/2/22 15:16
#217
|
Not too shy to talk
|
@freddix Quote: if comparizon need == instead of simple =. That's not exact. "==" is always a comparison, no matter where used and "=" is always an assignment, no matter where used. Unlike other programming languages, it is not related to "if" (or other places where conditions are used like "while" or "for"). Bye, Thomas
|
|
|
|
Re: It's "losing" not "loosing"
|
Posted on: 2009/2/22 15:12
#218
|
Not too shy to talk
|
@Antique Quote: But i think people understand what others write. Yes, but nevertheless it is a good thing to be corrected by native speakers. Being out of school for nearly 20 years and living in the center of europe, it is not easy to improve your english language if nobody corrects you. Bye, Thomas
|
|
|
|
Re: AmigaForever ROMs with Minimig
|
Posted on: 2009/1/24 10:36
#219
|
Not too shy to talk
|
@Elwood
Thinking about it, the minimig emulates an A500, doesn't it ? Then not all ROMs will work because they are from different Amiga models. For example the 3.1 ROM is from an A4000 and needs at least a 68020 processor.
Bye, Thomas
|
|
|
|
Re: AmigaForever ROMs with Minimig
|
Posted on: 2009/1/23 15:16
#220
|
Not too shy to talk
|
@Elwood
Except of the 3.X ROM all AF ROMs are the same as the original chip versions. But they are encrypted, you have to decrypt them first. For example, run WinUAE with the encrypted ROM and then use transrom to save the decrypted ROM.
Bye, Thomas
|
|
|
|