Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
95 user(s) are online (55 user(s) are browsing Forums)

Members: 0
Guests: 95

more...

Headlines

Forum Index


Board index » All Posts (thomas)




Re: Wildcards and special characters in shell
Not too shy to talk
Not too shy to talk



You don't need a special character to represent tab. Just press the tab key.

To escape the * character just enter another * (**).


Go to top


Re: lowlevel.library problem??
Not too shy to talk
Not too shy to talk



Printf (with upper case P) ist just fine.

You need to understand that lowlevel.library does not capture input. It just returns the state of input devices at a very low level. It does not influence the input stream in any way.

So if you press any key while the CLI window is active, the key will be printed into the window and output is stopped. In order to continue output you have to delete the printed keys. That's the same with all non-dead keys on the keyboard.


Go to top


Re: lowlevel.library problem??
Not too shy to talk
Not too shy to talk



I cannot verify if it does the same because I am not sitting at my A1 right now, but this is basically the program of Alfkil:

#include <proto/dos.h>
#include <proto/lowlevel.h>

int main (void)

{
ULONG key;

do    {
    
Delay (10);
    
key GetKey();
    
Printf ("0x%08lx\n",key);
    }
while (
key != 0x45);

return (
0);
}

Go to top


Re: lowlevel.library problem??
Not too shy to talk
Not too shy to talk



The function is documented to return the currently pressed key. It does not say that you need to keep polling until no more keys are pressed. It also says nothing about the maximium time between calls.

This means the function needs to return the current keyboard state even if it is called only once. How this is implemented is up to the maintainer of the library, not of the application programmer. If the library does not recognise key-up events after the application ends (or if the application is busy), this clearly is a bug.


Go to top


Re: lowlevel.library problem??
Not too shy to talk
Not too shy to talk



Ok, I tried WinUAE and there it works correctly. On OS4 (A1XE) it does what you say.

If you hold down the Esc key before the second run and lift it before the first message appears, the program continues with 0xff until you press Esc again.

So it seems like lowlevel.library only records events while a program is using it. As you leave the program when Esc is pressed, it does not recognise the release of the key.


Go to top


Re: lowlevel.library problem??
Not too shy to talk
Not too shy to talk



Amiga model?
OS version?
lowlevel.library version?

Go to top


Re: lowlevel.library problem??
Not too shy to talk
Not too shy to talk


The debug_buffer is too short. You reserve 10 bytes but write 12 bytes (0x12345678, lf, 0). For me it prints two lines and then crashes. It does not crash if I comment the jsr debug_write_ulong and it works correctly if I increase the buffer to 20.


Go to top


Re: OS4 and home network
Not too shy to talk
Not too shy to talk



Samba is a SMB server. You cannot connect to another server with a server application. You need a SMB client to connect to your NAS. SMB clients for AmigaOS are for example SMB-Connect or SMBFS. The latter exists OS4-native.

Go to top


Re: FIND dos command
Not too shy to talk
Not too shy to talk



Quote:
The example is: foo(%|.info)


This works as well: foo(|.info)
I never needed to put a % sign in there.

Go to top


Re: FIND dos command
Not too shy to talk
Not too shy to talk


1) try ~(#?)

Why do you think that % is a wildcard?


Edit: sorry, ~(#?) will only list those without a comment. Try ?#? to get those with at least one character.



Edited by thomas on 2011/10/17 13:54:00
Go to top


Re: Insert volume CONSOLE: error
Not too shy to talk
Not too shy to talk



CONSOLE: is not an assign, it is a file name which points to the console window the program was started from. Just like "*" did in early AmigaDOS versions.


Go to top


Re: MaxTransfer rate for SATA?
Not too shy to talk
Not too shy to talk



There shouldn't be any need to change the default values. Only badly written drivers need adjustments in MaxTransfer and Mask.

Go to top


Re: IDETool
Not too shy to talk
Not too shy to talk



It's there since the first release of 4.0, so I assume yes, it's standard.


Go to top


Re: Poll: Did you use the Network Wizard for Update 3?
Not too shy to talk
Not too shy to talk



Why should I? My previous network connection still works without problems.

BTW, I voted three times now and still cannot see any results.

Go to top


Re: Why not porting EASy68K?
Not too shy to talk
Not too shy to talk



Why do you think this would be of any use? It is not related to Amiga in any way. It simulates (not emulates) a custom hardware which looks quite simple, but is in no way compatible to Amiga hardware. A program written for this virtual hardware would not do anything meaningful on an Amiga if it would run at all.


Go to top


Re: MUI event handling kludge mystery
Not too shy to talk
Not too shy to talk


You should divide "sigs" into "signals_to_wait_for" and "signals_received". Otherwise you overwrite your variable and at some point sigs is 0 and Wait(0) will never return.

BTW, you should remove the Wait() from the "seperate procedure".

Go to top


Re: Where's Aminet ????
Not too shy to talk
Not too shy to talk



There is an official statement at amiga-news.de:

http://translate.google.de/translate? ... FAN-2011-08-00062-DE.html


Go to top


Re: Finding size of system font?
Not too shy to talk
Not too shy to talk



Please define "system" font.

Please define "size".

The font that usually is called the "system font" is the fixed-width font you define in Prefs/Font. It is the default font for all RastPorts, but it is not used for GUI elements. The default font for GUI elements is the screen font. You can get it from Screen->RastPort.Font (pointer to struct TextFont) or Screen->Font (pointer to struct TextAttr).

The size of a font usually means its height. Therefore you can get the size of a font from TextFont->tf_YSize or TextAttr->ta_YSize. Or Screen->RastPort.TxHeight.

If you want the width of a given text you should use the TextLength function.

Some fonts, especially outline fonts, might need more pixels than derived from TxHeight / TextLength. To get the real area a given text needs to be printed, you should use the TextExtent function.

Go to top


Re: Escape code for % in shell
Not too shy to talk
Not too shy to talk



%% should give you a percent sign.

BTW, %p%s is a mixture of "old" and "new" style. %s is WB 1.3 style which alternates between path and file name (i.e. use %s%s to get path and file name). You should use %p%n to get path and file name. These exist since WB 2.0.


Go to top


Re: ReadArgs()
Not too shy to talk
Not too shy to talk


Quote:
initialising args solves this behaviour it seems


Yes, you need to initialise the argument array with your defaults. Fields that do not appear in the command line remain unchanged.

Go to top



TopTop
« 1 ... 3 4 5 (6) 7 8 9 ... 14 »




Powered by XOOPS 2.0 © 2001-2023 The XOOPS Project