Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
106 user(s) are online (66 user(s) are browsing Forums)

Members: 0
Guests: 106

more...

Headlines

Forum Index


Board index » All Posts (saimo)




Re: Icon Wunschkonzert - AISS Edition
Quite a regular
Quite a regular


@Wanderer

Quote:
The idea with this Library was not to "route" the AB3 functionality to the outer world. I don't think that somone would make use of such a library as an image-processing library, unless he codes in Amiblitz and then he doesn't need a library. If you code in C, you don't want to use a 68K Library for main things.

The idea is to complete AISS by having an interface to access the images. Not everybody is firm in laoding and blitting images with alpha channel.
There are a lot of glitches if you want to make it work 100% correctly on OS4, MOS and OS3.
The library provides scaling and caching, so that two programs won't load the same images 2 times. The images processing is just a gimmik for those who feel they want to manipulate the images. The most important here is to make the selected state easily identifiable, e.g. with a glow effect or a color change with tinting or background., and do the background/foregroudn composing for you like Mason suggested with the Aqua bubble.
It really should be something that deals with your GUI images. I think e.g. of a filemanager, that can display the icons scaled to the fontsize next to the filename etc., or has different views like the windoze explorer with different icon sizes.

I know that this is no real magic, but the library can do this for you in high quality and you dont have to fiddle around with datatypes, icons and scaling code.

Sorry, in my previous comment I overlooked the caching aspect. Still, your library is naturally not stuck to GUI stuff. Basically, you have: image loading, image processing, image caching. These are general purpose functions that can be used for anything, not just GUI elements. Your idea could implement a nice service for the OS - the more I think of it, the more I'm convinced AmigaOS and its applications would greatly benefit from an easy to use, efficient, flexible way for handling images.

As regards AmiBlitz, well, that's good for a proof of concept / starting up, but in the long run a native solution is certainly desirable.

Quote:
I never programmed Reaction, so I dont know how to this and I dont know how to write boopsi classes. It will anyway not be accepted unless it is "native". So I think the most flexible is to provide the BitMap that can be used for further processing.

Precisely: you provide the layer for images handling (as said, loading, processing, caching), the rest is built on top.

BTW: I did not mean to ask you to make a toolbar Reaction class - that was just a think-aloud request

saimo

Go to top


Re: AmigaOS 4.1 - software problems.
Quite a regular
Quite a regular


@drHirudo

Quote:
E-UAE on AmigaOS 4.1 crashes when opening the config file,

Not here (even when feeding it with two configuration files).

Quote:
if you delete the config file or start it from the config GUI it works right away.

I always start it from shell (mostly through glUAE) and, as said, only the stack may cause problems.
Maybe configuration options have something to do with the problems you are experiencing.

saimo

Go to top


Re: Icon Wunschkonzert - AISS Edition
Quite a regular
Quite a regular


@Wanderer

Quote:
yes, renamed AISS => TB for now.

(toolbar.library)

I hope there is no toolbar.library out there yet...

I think such name is not suitable: you are basically focusing on applying dynamically effects on images and not on handling toolbars - I'd say something like imageseffects.library is more appropriate. Sure, your library could be used for images in toolbars, but that's a whole another story: it could also be used, for example, for icons or by applications to apply those effects to their images even for reasons other than GUI. Basically, I think you'd better aim for a general-purpose image processing library (and yes, it is perfectly OK if you start implementing simple, GUI-oriented effects).

As regards toolbars, instead I hope that sooner or later a proper class is added to Reaction.

saimo

Edit: fixed grammar junk


Edited by saimo on 2008/9/26 13:27:13
Go to top


Re: Icon Wunschkonzert - AISS Edition
Quite a regular
Quite a regular


@Wanderer

Quote:
Doest that sound cool or do you have any suggestions/wishes?

I could not pay the API the due attention, but at the first glance it looks nice. Suggestion: drop the explicit reference to AISS - as you said yourself, you library has a general characterization

Keep up the good work!
saimo

Go to top


Re: AmigaOS 4.1 - software problems.
Quite a regular
Quite a regular


@Skov

Quote:
Doesn't work... It crashes...

Then I can't help, sorry.

Quote:
Would it help to see crashlogs?

Before posting them here, you'd better show them to Richard Drummond (maybe it is not a problem with the OS).

Quote:
Oh, I am running WIP4... should I go back to WIP3?

LATEST NEWS - download .28 instead of .29... and it works! Great!

And Amigainput works with this nice joypad I bought!

Here version 0.8.29-WIP4 runs happily (except for the mentioned stack issue), but I do not use AmigaInput: maybe that's where the problem is? Could you try running version 0.8.29-WIP4 without AmigaInput (move the preferences temporarily somewhere else and make sure you start E-UAE without any gaming device plugged in)?

saimo

Go to top


Re: AmigaOS 4.1 - software problems.
Quite a regular
Quite a regular


@Ricossa

Quote:

Ricossa wrote:
@abalaban

no because the GR appears at re-booting time. I have to save the prefs and then reboot. If I only do a "use", everything is ok

So, let me get it straight: if you *boot* from CD it's OK, but if you *reboot* from CD it's not? - smells like you have mixed Kickstart modules (yes, I've read that you made a clean installation, but this last post of yours hardly makes sense to me...).

saimo

Go to top


Re: AmigaOS 4.1 - software problems.
Quite a regular
Quite a regular


@Skov

Quote:

Skov wrote:
Can anyone get E-UAE to run on OS4.1?

Mine crashes everytime... First it gives a DSI-error and then - after pressing ignore - an ISI-error...

I've tried increasing the stack to over 500000...

What to try next, guys?

Raise the minimum stack to 32 kb (already mentioned in this very thread - seizing the chance to ask again: wasn't automatic stack enlargement to be in place?).

saimo

Go to top


Re: AmigaOne U-Boot bugs - please read
Quite a regular
Quite a regular


@Rogue

Quote:

Rogue wrote:I just tested, my drive here takes about five seconds with or without a CD.

Ah, yes, I forgot to mention that that's without CD in.

Quote:
That happens to be the timeout of the ATAPI code. If you drive takes that long, it's a problem with the drive, and I won't be able to do anything about it.

mmm... if 5 seconds is the timeout, how come checking goes as far as 13 seconds (of course I prefer a longer wait than a non-recognized drive )?
One more thing I forgot: at some point I got my U-Boot chip replaced (that's why I happen to have version 1.1.4 instead of 1.1.1) and I'm almost sure that the wait was only 7 seconds before - i.e. version 1.1.4 could have done things worse.
Oh, well. It's not that important. Just keep it in mind in case you spot something not quite right

Quote:
About the variables, just delete them.

That's what I do. I was pointing them out just to allow you to do some cleaning up.

saimo

Go to top


Re: AmigaOne U-Boot bugs - please read
Quite a regular
Quite a regular


@Rogue & moderators

Is it OK to discuss issues? Or would it be preferable to use this thread for reports only?
In the meanwhile, I hope you don't mind if I answer Renoir...


@Renoir

Sorry if these questions sound obvious, but I guess it's better to make sure your problems lie in U-Boot and not somewhere else.
The Kickstart is launched by the SLB (not U-Boot): are you sure you have the right version installed? Does Kickstart launching start altogether? If yes, does it halt immediately or at some point? Have you modified the Kicklayout?

saimo

Go to top


Re: AmigaOne U-Boot bugs - please read
Quite a regular
Quite a regular


@Rogue

First off, thanks for giving us this possibility
As regards my issues with U-Boot, they are not that important, but since you asking...


Machine: A1 XE G4@1GHz
U-Boot version: 1.1.4 (Mar 16 2006 - 12:23:46)


My "major" problem is that initialization of my DVD drive takes some 13 seconds (that's a relevant part of the 36 seconds it takes to cold-boot - it bugs me when I start the machine and does not allow me to impress people even more ), whereas the CDRW and HD initialization is practically immediate.

All of the devices are mounted on a Silicon 680 card, more precisely a Q-TEC 340R.
For cables length reasons, the layout is as follows:
- primary master: CDRW;
- primary slave: DVD;
- secondary master: HD;
(corresponding U-Boot variables: sii0680ide_conf=2210, sii0680ide_xfer=CCG0).

The DVD is an Artec 16x drive, which U-Boot describes with this string: Vendor: IDE Prod. : DVD-ROM 16x Rev: 2.02
Idetool returns the following (correct) parameters:

Quote:
Flags : $0000011D - present, supports DMA, removable media, ATAPI, interrupts used,
Xfer mode : best pio 12 (PIO 4, 16 MB/s) / best dma 66 (UDMA 2, 33 MB/s) / current 66 (UDMA 2, 33 MB/s)
Total blocks : 0
Blocksize : 0
SCSI devtyp : 5
Packet size : 12
Current medium read speed : x 65535 ('65535' stands for max.)
Current medium write speed : x 65535 (idem)
Power mode : 2 / idle (ready for operation)
IO1 / IO2 / BMCR @ : $8020C0 / $8020CA / $8020E0

No other drives are mounted (including the floppy drive).
Other than the initial delay, the drive works fine.


My "minor" problem is that, I think, there are some leftovers from the previous versions. I cannot be 100% accurate because most of what follows comes off the top of my head.
IIRC (some of) the ide_* variables have been obsoleted by the a1* and sii* ones (although I keep some of them set for some reason I cannot remember), but the graphical menu still sets and saves them (I can't really tell because since I found the menu clutters the environment, I stopped using it). Same goes for (some of) menucmd, bootmethod, boot_method, menuboot_cmd, boot_command: I can do without them and I guess that, even if I used the graphical menu, not all of them would be needed.
In short, I'd suggest a little cleanup.
Just in case you may need it, here is my full U-Boot environment:
Quote:
bootargs=root=/dev/ram rw ramdisk=4096
bootdelay=0
baudrate=115200
stdout=vga
stdin=ps2kbd
ethact=3Com 3c920c#0
kbddev_sysreqishelp=yes
ide_doreset=on
ide_cd_timeout=30
sii0680ide_maxbus=2
sii0680ide_timeout=5
bootcmd=boota
boot2=psiicdrom
boota_timeout=1
video_activate=agp
serial1_address=3f8
serial2_address=2f8
parallel_mode=1
parallel_address=378
usb0_enable=on
usb1_enable=off
usb_use_header=0
ethaddr=00:09:D2:11:01:15
ipaddr=<unset>
serverip=<unset>
menuboot_delay=0
pci_irqa=9
pci_irqa_select=level
pci_irqb=10
pci_irqb_select=level
pci_irqc=11
pci_irqc_select=level
pci_irqd=7
pci_irqd_select=level
agp_enable=on
agp_speed=2x
limit_memory=256
use_memory_limit=no
ide_maxbus=0
sii0680ide_conf=2210
sii0680ide_xfer=CCG0
bootdevice=2:1
boot1=psii
agp_sideband=on
video_num=1
os4_commandline=debuglevel=0

(just noticed I could probably remove bootargs, ide_maxbus and agp_sideband).


Hope this helps,
saimo

Go to top


Re: AmigaOS 4.1 - software problems.
Quite a regular
Quite a regular


@abalaban

Quote:
Then you were not using the latest OS 4.0, this is there since we can use Monitor icon to control the modes, instead of PicassoMode...

I was definitely using the latest public version of AOS 4.0. If I get a chance, later I'll reinstall it to make sure it's not just my memory failing me.


Quote:
How would you want it to be done ? Using the tooltype way of configuring the devs should assign a unique screenID to each of the screen mode listed in your icon, they do it by using the range of the mode in the icon.

Including a mode index in the ID is completely useless, as what characterizes modes are their properties - in other words, only properties (sizes, depths, frequencies) are strictly needed to describe the mode. The index only helps distinguishing between identical modes specified more than once: but even in that unlikely case, there would be no problem, as the system would be able to detect the duplication right from the start - and even if duplication weren't taken care of, things would just naturally work anyway.

saimo

Go to top


Re: AmigaOS 4.1 - software problems.
Quite a regular
Quite a regular


@salass00

Quote:
This problem is not unique to OS4.1.

Well, it did not happen on 4.0 - not on my system, at least.

Quote:
Just add new modes to the end of the list and you won't have this problem anymore.

OK, but this is just a workaround. I hope developers will fix the problem.

saimo

Go to top


Re: AmigaOS 4.1 - software problems.
Quite a regular
Quite a regular


Adding/removing modes from the monitor tooltypes completely changes the IDs of the other modes - this fools the applications that store mode IDs in their settings, including the screenmode preferences!

F.ex.:

MODE=320x256x8,32@60
MODE=640x480x8,32@60
MODE=1280x768x8,32@60 -> ID: 0x50021300

MODE=320x256x8,32@60
MODE=320x300x32@60
MODE=640x480x8,32@60
MODE=1280x768x8,32@60 -> ID: 0x50031300

saimo

Go to top


Re: Icon Wunschkonzert - AISS Edition
Quite a regular
Quite a regular


@jaokim

Real-time glow would be a nice option, however it would look bad with those icons that have a shadow - Mason, I'm pointing this out just to suggest you to remove shadows: icons will look just as nice, will look fine in any context and will be less work for you when creating new ones

I'll seize the chance to express my opinion on a related subject - I know many (most of the) Amigans will not agree, but here it comes anyway...
Replacing alternate icons with a real-time plugin-based selected-state system* (so that the selected state would be calculated on the fly by applying a "selected" effect), would save Mason and whoever creates icons a lot of work and pain (thus enabling them to draw more icons and update the current ones with much less effort) and would help keeping a consistent look'n'feel throughout the system. Basically, this is already what happens currently when icons have no alternate image, only that there is only one fixed effect.

Edit: *implemented directly in the icon system.

I'm perfectly aware that this means giving up on a peculiarity of AmigaOS icons, so - as said - I do not expect this suggestion to be popular. I'm making it anyway only because its advantages are great and the flip side is just losing something which, IMHO, is mostly eye candy.

saimo

Go to top


Re: AmigaOS 4.1 - software problems.
Quite a regular
Quite a regular


This one may be a sign of some serious problem: sometimes the launch of programs (mostly from AmiDock, but I think it also happened once or twice from WB and/or shell) is delayed for a 5 or so seconds (with the machine doing nothing else and plenty of RAM free).
This may cause the "lost click" effect mentioned somewhere else.

BTW: is any OS developer/betatester taking note of all that's being reported in this thread?

saimo

Go to top


Re: AmigaOS 4.1 - software problems.
Quite a regular
Quite a regular


More problems, with layers/composition this time: sometimes some areas are not updated/refreshed.
For example, 3 or 4 times when I clicked on an item in a WB window in TextMode mode only the hightlight got drawn (i.e. the item name and properties did not get redrawn): look at this grab.
Funnily and fittingly, when I dragged and released the file of the picture above into the ASL requester opened by IBrowse precisely to upload the picture, the ASL requester did not get refreshed at all; but it did refresh when I selected the ASL window itself (which appeared unselected precisely because it did not get refreshed). This had happened before also when I uploaded AOS 4.1 grab here on AW.net.
A similar problem had happened with ClassAction, but I did not give it much importance because it is a M68k application.

Maybe there is more than one problem (f.ex. lost notifications), but for sure the effect is the same.

Hope this helps.
saimo

Go to top


Re: AmigaOS 4.1 - software problems.
Quite a regular
Quite a regular


@acefnq

You're welcome


@mufa and/or admins
What about updating the first post with a comprehensive list of all the problems found?

saimo

Go to top


Re: AmigaOS 4.1 - software problems.
Quite a regular
Quite a regular


@Ricossa

Quote:
In Prefs/Workbench/text-mode, if I set the small icons to anything else than "disabled", I get a grim reaper from C:IPrefs everytime I boot the A1 (equal if cold or warm reboot). Hitting "ignore dsi" makes it work.
Setting back the small icons to "disabled" fixes the problem.
Am I alone with this ?

I add this : I have set a custom background colour. May be it has something to do with the strange grimming IPrefs ?

If the problem were the background, your system would be much more instable
As for the icons problem, sorry, I cannot help. Here it just works (although I keep it off, as the type column does the job better without cluttering the view).

saimo

Go to top


Re: AmigaOS 4.1 - software problems.
Quite a regular
Quite a regular


Dunno if this is a bug or a change of behaviour, but anyway...
- ENV: now mirrors ENVARC: right from the start (i.e. it is not filled on demand).

Edit: add to that this one (a real bug):
- mouse wheel does not break screenblanker countdown.

saimo

Go to top


Re: AmigaOS 4.1 - software problems.
Quite a regular
Quite a regular


@abalaban

Quote:
Here after a clean install and on an FFS partition, WB text mode shows my links to drawers perfectly however this is ASL that does not...

So, you have the exactly opposite problem (i.e. TextMode OK, ASL wrong)?

As for me, I just discovered that the only thing TextMode gets wrongs is the color of links to drawers: now I tried italicizing them and it works. This means that links are correctly recognized as such. Basically, the custom color is ignored when it comes to drawers.

As regards filesystems, I still think that this issue has nothing to do with them, not only because link do get recognized, but also because the behaviour is the same for both the RAM disk (FFS, IIRC) and my HD partitions (all SFS).

saimo

Go to top



TopTop
« 1 ... 26 27 28 (29) 30 31 32 33 »




Powered by XOOPS 2.0 © 2001-2023 The XOOPS Project