Who's Online |
88 user(s) are online ( 51 user(s) are browsing Forums)
Members: 0
Guests: 88
more...
|
|
Headlines |
-
snes9x.zip - emulation/gamesystem
Apr 29, 2024
-
hle-pokercard.lha - game/card
Apr 29, 2024
-
mce.lha - game/utility
Apr 29, 2024
-
amiarcadia.lha - emulation/gamesystem
Apr 28, 2024
-
ifarchive_dl.lha - utility/script
Apr 28, 2024
-
kt_scripts.lha - utility/script
Apr 28, 2024
-
stream.lha - utility/benchmark
Apr 27, 2024
-
thumbnailmaker.lha - video/misc
Apr 26, 2024
-
theme_list.lha - utility/misc
Apr 23, 2024
-
faac.lha - audio/convert
Apr 22, 2024
|
|
|
|
Re: Output window
|
Posted on: 2009/4/22 19:44
#1001
|
Just can't stay away
|
@orgin Quote: but then you're back to the sticky-won't -die-whatever-the-user-does-damnit window. Please post a small example which has such a problem. At least with simple tests like the following I can't reproduce such a problem here, when starting the program from Workbench closing the console window works and it's reopend when there is new output:
#include <stdio.h> #include <unistd.h>
int main(void) { int i; for (i = 1 ; i <= 10 ; i++) { printf("%d\n", i); sleep(2); } return 0; }
|
|
|
|
Re: The MUI vs Reaction slapfest thread (was OWB 3.6)
|
Posted on: 2009/4/22 16:21
#1002
|
Just can't stay away
|
@Crumb Quote: The difference is that it's easy to create new MUI custom classes. Easy, but still more work than creating new standard BOOPSI custom classes. There are 2 more reasons why I'll never do anything with MUI on AmigaOS 4.x: - To use MUI in AmigaOS 4.x software you first have to create an AmigaOS 4.x MUI SDK yourself, the existing one can only be used for compiling old AmigaOS 3.x sources (it only works when using -D__USE_INLINE__). - To create MUI custom classes you have to register MUI. Quote: E.g. check out AROS OWB port with custom tab class that allows adding/removing tabs That's just another reason against using MUI or Zune: To be able to use tabs he had to create a new tab class, the ones of MUI and Zune don't support dynamically adding and removing tabs and therefore couldn't be used for OWB. The AmigaOS 4.1 clicktab.gadget supports dynamically adding and removing tabs and I didn't have to implement my own one.
|
|
|
|
Re: Output window
|
Posted on: 2009/4/22 3:39
#1003
|
Just can't stay away
|
@orgin Quote: I've noticed that you can't close the output window that you get when writing to stdout/stderr. Strange, it's still working here. If you just want to use a different CON: for C library stdio when the program is started from Workbench, i.e. you don't need to change it dynamically, add a global __stdiowin variable in your program with the file name, for example const char *__stdiowin = "CON:64/48/800/200/foobar output/AUTO/CLOSE/WAIT"; If you need to change it dynamically you have to freopen() stdout and/or stderr.
|
|
|
|
Re: OWB 3.11
|
Posted on: 2009/4/21 1:16
#1004
|
Just can't stay away
|
@lazi Quote: May I ask for a bit explanation for the following error message?
Loading http://www.khb.hu/ failed. peer certificate cannot be authenticated with known CA certificates The page forwards to a HTTPS one and the certificate for it can't be verified. You can use "setenv WEBKIT_IGNORE_SSL_ERRORS 1" in a shell before starting OWB to access the site, but since that disables the security checks you better shouldn't do it for such a site ... Quote: Is there something that I can add to ca-bundle.crt to solve this? It's about 5 months old, could be that a newer version includes the required certs, but I didn't check it.
|
|
|
|
Re: Filesystem links
|
Posted on: 2009/4/19 18:09
#1005
|
Just can't stay away
|
@Chris Quote: Hmm, well there's something wrong as if I create a file "test1" makelink test2 test1 and then edit test2, the contents of test1 don't change as they should. If you change test2, for example using "echo >>test2 foobar" in a shell, the contents of both changes. Most editors don't change the file, they delete the old one and create a new one instead and if that's done test1 and test2 are of course different files, for example "echo >test2 foobar" in a shell does that as well.
|
|
|
|
Re: Filesystem links
|
Posted on: 2009/4/19 17:01
#1006
|
Just can't stay away
|
@Chris Quote: On JXFS if you try to create a hard link, it just creates a copy of the file instead. No, it creates a hard link. Just a real one, like for example on Unix, not the weird FFS hard links, and most AmigaOS programs can't identify them as hard links (ExamineData UseCount is > 1 and all directory entries have the same ObjectID).
|
|
|
|
Re: Filesystem links
|
Posted on: 2009/4/19 3:19
#1008
|
Just can't stay away
|
@orgin Quote: 2. Creating a hardlink to a file in ram: and then editing the file (not the link) turns the hardlink into a file. (odd but perhaps normal?) With FFS and ram-handler: Yes. They don't have usual hard links but a strange implementation which only exists on AmigaOS, one of the links has to be a file and if you delete the link which is currently the file one of the other links has to be converted into a file instead.
|
|
|
|
Re: OWB on Pegasos2 (slow down bug?)
|
Posted on: 2009/4/15 23:48
#1010
|
Just can't stay away
|
@kas1e Quote: @joerg my SYSTEM: are FFS with 1024 blocks. Tryed as you said: add buffer TBImages: 10000, and nothink (the same). It probably doesn't make a very big difference when starting OWB, FFS simply is that slow, but it should when iconifying and uniconifying OWB. Additonally make sure you have DMA enabled. Another way to check if it's related to the AISS images is disabling AISS (use "assign TBImages:" in a shell) before starting OWB. If it doesn't make any difference the delay is not related to the loading of the AISS images.
|
|
|
|
Re: OWB on Pegasos2 (slow down bug?)
|
Posted on: 2009/4/15 17:52
#1011
|
Just can't stay away
|
@kas1e Quote: Already have 512 blocks (512 blocks must be for 'system' partition, or for partition on which i have unpacked owb?). But you are right about AISS i think .. maybe need install new one or older one Especially if your SYS: (or wherever you have AISS installed if you didn't use the default) partition is FFS you are using way too few buffers for it, try again after using "Addbuffers TBImages: 10000" in a shell.
|
|
|
|
Re: About window on OWB
|
Posted on: 2009/3/27 1:01
#1012
|
Just can't stay away
|
@nbache Quote: It's one of the external links on the wikipedia page, but another one, http://www.sveinbjorn.org/dataurlmaker , seems to be more reliable.
|
|
|
|
Re: About window on OWB
|
Posted on: 2009/3/26 0:56
#1013
|
Just can't stay away
|
@samo79 Quote: @joerg Quote:Everything has to be inline, incl. all images (img/bg_orange.png, img/logo.png, img/paypal.png). You have to use data: URLs for them. Mmmm can you post me an example ? http://en.wikipedia.org/wiki/Data_URI_schemeQuote: And more important do you plan to release an updated release anytime soon ? Yes.
|
|
|
|
Re: About window on OWB
|
Posted on: 2009/3/24 3:27
#1014
|
Just can't stay away
|
@samo79 Quote: 1 - Now I use CSS and Javascript "inline" in order to fit in OWB archive (Joerg need that) so now we have all HTML/CSS/Javascript code in the same HTML page. Everything has to be inline, incl. all images (img/bg_orange.png, img/logo.png, img/paypal.png). You have to use data: URLs for them. Quote: Now I need your help as I can't try OWB myself. Why? Since it doesn't use anything special it works with the ancient OWB Blastoise as well and you can even test it with the AmigaOS 3.9/m68k port of OWB on UAE. Or use any other WebKit based browser (Safari, Chrome, Epiphany-webkit, Arora, ...) for testing it. Quote: Any other problem or suggest are welcome There is no DejaVu font family, the ones included in AmgaOS 4.x are "DejaVu Sans", "DejaVu Sans Mono" and "DejaVu Serif". Additionally using sans-serif (Tahoma, Verdana, sans-serif) and a serif ("Times New Roman") one for the body,td,th font-family doesn't make sense!?
|
|
|
|
Re: Is this a bug? FOpen()
|
Posted on: 2009/3/19 17:29
#1015
|
Just can't stay away
|
@orgin Quote: I just tried on a hard drive partition with SFS and it didn't respect the write flag at all (SFS). Of course not. Unlike for example Unix AmigaOS has separate write and delete permissions. [F]Open("ExistingFile", MODE_NEWFILE) is a delete (+ create new file) operation, not a write (something to an existing file). Quote: The file was overwritten without any error (including comment, date and protect flags) Unless you copy them from the old file the new file has the default protection bits (for example ---- ---- ----rw-d), comment (none), date/time (current time), etc. To get what you expect, modifying an existing file instead of replacing it with a new one, you have to use something like file = IDOS->FOpen("foobar", MODE_READWRITE, buffersize); IDOS->ChangeMode(file, CHANGE_FH, EXCLUSIVE_LOCK); IDOS->ChangeFileSize(file, 0, OFFSET_BEGINNING); instead, which works on delete protected but not on write protected files and keeps the protection bits, comments, user/group, etc., instead of using file = IDOS->FOpen("foobar", MODE_NEWFILE, buffersize) which replaces the file with a completely new one (unless the old one was delete protected).
Edited by joerg on 2009/3/19 17:45:01 Edited by joerg on 2009/3/19 17:45:57
|
|
|
|
Re: Lock() problem
|
Posted on: 2009/3/14 0:28
#1016
|
Just can't stay away
|
@orgin Quote: I'm trying to determine what kind of object a path is by using either
Lock(path,SHARED_LOCK)+ExamineObjectTags(EX_fileLockInput...)
or
ExamineObjectTags(EX_StringNameInput,...) Neither of both can work since they need an additional lock (internally) which isn't possible for files opened with an exclusive mode like MODE_NEWFILE, you have to use IDOS->ExamineObjectTags(EX_FileHandleInput, ...) instead. Or open the file in shared mode (MODE_READWRITE). Or open it in exclusive mode but change it to shared with IDOS->ChangeMode(CHANGE_FH, file, SHARED_LOCK) after it was opened successfully.
|
|
|
|
Re: OS 4.1 and Blu-Ray
|
Posted on: 2009/3/11 16:22
#1017
|
Just can't stay away
|
@nubechecorre Quote: I know ( that what is written in the readme file ), that amiddvd support Blu-ray and you can burn software on blu-ray disc AmiDVD does not support Blu-ray burning. The supported formats are CD-R, CD-RW, CD-RW MRW, DVD+R, DVD+RW, DVD+RW MRW (untested), DVD+R DL, DVD-R, DVD-RW and DVD-RAM, everything else (DVD-R DL, DVD+RW DL, DVD-RW DL, HD DVD, Blu Ray, ...) can't be used. Quote: but you have the limit of 4 Gb.. Wrong, AmiDVD supports large files. Of course that only works if you are storing the image file on a partition with a file system which supports files >4GB as well (SFS\2 or JXFS).
|
|
|
|
Re: OWB 3.7
|
Posted on: 2009/3/2 21:32
#1018
|
Just can't stay away
|
@Gebrochen Quote: Id much rather open up a browser that has the support in it already. Simply do it, there are several AmigaOS browers which support downloads, for example AWeb, IBrowse and NetSurf. Quote: Another note would be, many may not like fiddling around hours at a time for little things like downloading, or getting other programs to work. I do it nonetheless, but if the majority of the users would be like you I wouldn't waste my spare time writing/porting free software for/to AmigaOS, especially implementing features I don't need myself, any longer.
|
|
|
|
Re: OWB 3.7
|
Posted on: 2009/3/1 20:00
#1019
|
Just can't stay away
|
@COBRA Quote: Do you have any idea about the strange event problems? I didn't even know there are problems, there is no bug report on http://bugs.os4depot.net/?function=viewissues&softwareid=1Quote: It seems as if sometimes OWB enters a mode in which it interprets single-clicks as double-clicks. Since I have a very short double click time configured in Prefs/Input I never noticed the problem myself, but I've fixed it now. The double- and triple-click checks only used the time (IIntuition->DoubleClick()), in the next version they will only be recognised as double- or tripple-clicks if the mouse pointer was moved at most 3 pixels.
|
|
|
|
Re: OWB 3.7
|
Posted on: 2009/3/1 18:44
#1020
|
Just can't stay away
|
@Raziel Quote: Check AbeBooks and click Warenkorb on the upper right ... OWB will sit there trying to load it ... and i sit there waiting forever for it to finish.. The next version of OWB will display network errors, in this case "peer certificate cannot be authenticated with known CA certificates". You can use "setenv WEBKIT_IGNORE_SSL_ERRORS 1" in a shell before starting OWB to accesss pages with such SSL problems.
|
|
|
|