Who's Online |
153 user(s) are online ( 110 user(s) are browsing Forums)
Members: 0
Guests: 153
more...
|
|
Headlines |
-
mce.lha - game/utility
Apr 23, 2024
-
theme_list.lha - utility/misc
Apr 23, 2024
-
faac.lha - audio/convert
Apr 22, 2024
-
faad2.lha - audio/convert
Apr 22, 2024
-
seq.lha - audio/misc
Apr 22, 2024
-
libfaac.lha - development/library/audio
Apr 22, 2024
-
libfaad.lha - development/library/audio
Apr 22, 2024
-
image2pdf.lha - utility/text/convert
Apr 22, 2024
-
libharfbuzz.lha - development/library/graphics
Apr 20, 2024
-
libpng.lha - development/library/graphics
Apr 20, 2024
|
|
|
|
Re: Dockies with new SDK
|
Posted on: 2009/2/15 18:56
#121
|
Just popping in
|
@Cyborg
With the new Amidock (OS4.1), in the rendering mode that used to be pseudo-alpha but seems now to be real alpha, dockies are drawn differently depending on whether Intuition uses compositing or not (regarding the alpha channel). Is there a way to get around this ?
Example : when drawing a picture with an alpha channel to the docky rastport (e.g. an AISS bitmap), with compositing off the result is the one expected, whereas with compositing on the docky is partially transparent (one can see the dock background) near the outlines of the picture, where alpha is not 1.
|
|
|
|
Re: Dockies with new SDK
|
Posted on: 2009/2/5 20:39
#122
|
Just popping in
|
@Curty
If the docky is rejected by Amidock it could be related to the version number (has to be V50+) or to the lib name (has to match the name of the docky file).
|
|
|
|
Re: Dockies with new SDK
|
Posted on: 2009/2/4 20:31
#123
|
Just popping in
|
@Curty Not directly related to the new SDK, but if compositing is enabled Amidock now seems to use the alpha channel when blitting the docky to its window. So if like me you didn't care about the high order byte, maybe your docky is transparent . (IMHO, this behaviour shouldn't be the default).
|
|
|
|
Re: Dock app icon menu (right click) ?
|
Posted on: 2009/1/2 12:52
#124
|
Just popping in
|
@TSK For a standalone docky, add this in DockyGet() method, tag DOCKYGET_ContextMenu: Quote: Object *item1 = PopupMenuItemObject, PMIA_Title, "Open Prefs...", PMIA_ID, PMID_PREFS, PopupMenuItemEnd;
IIntuition->IDoMethod((Object *)msgData, OM_ADDMEMBER, item1, TAG_DONE);
For an app docky, AFAIK the option is added automatically with the appropriate tag in RegisterApplication() and you have to handle the corresponding applib message.
|
|
|
|
Re: What to display with Ranger?
|
Posted on: 2008/9/27 17:37
#125
|
Just popping in
|
And U-boot is not a BIOS...
|
|
|
|
Re: Icon Wunschkonzert - AISS Edition
|
Posted on: 2008/9/20 18:25
#126
|
Just popping in
|
@Wanderer Quote: P.S.: how do other developers need access to the image?
Using ReAction's bitmap.image, for example. @mason A bitmap for a "CD Rip" button (maybe just the "sendtocd" bitmap with the arrow reversed ) Also, I think there's a mistake in the 4.5 distribution, the "popup" ghosted image is a copy of the "popwin" one. Good work!
|
|
|
|
Re: FTPMount feedback
|
Posted on: 2008/4/27 18:06
#127
|
Just popping in
|
@abalaban
Currently Ftpmount locks the doslist (indirectly through AddDosEntry()) when adding itself, which can cause a deadlock when the list is already locked, so maybe something could be improved there (using NonBlockingModifyDosEntry() ?).
|
|
|
|
Re: What to display with Ranger?
|
Posted on: 2008/4/20 12:41
#128
|
Just popping in
|
@ssolie
An option to sort libraries by extension, or better, a second column in the listbrowser telling the "type" of library for known extensions (with column sorting) : "BOOPSI gadget", "Datatype", "USB function driver", etc...
|
|
|
|
Re: A must-have for every OS4-Developer...
|
Posted on: 2008/4/3 19:49
#129
|
Just popping in
|
@abalaban Quote: abalaban wrote: I agree too but then we should have some kind of loading/caching mechanism because on my unfixed A1XE internal IDE the majority of application using AISS are really crawling at startup (20 seconds to load is not uncommon).
There is already such a system of shared bitmaps in OS4 intuition (don't know if ReAction uses it though).
|
|
|
|
Re: MP3 Encoding
|
Posted on: 2008/1/23 19:42
#130
|
Just popping in
|
@Valiant Quote: ADRipper looks like it might be a very good program, but I really can't tell. It immediately locks up my A1 upon startup.
Quote: Valiant wrote: @Swoop
I have AISS installed and it still happens.
Ouch! That definitively shouldn't happen, be AISS installed or not. Feel free to send me a log of the crash at the address mentioned in the archive (after a complete lock up, you can still generate a report typing "dumpdebugbuffer ram>log.txt clear" in a shell after a "soft" reset).
|
|
|
|
Re: DiscreetFX is evaluating toolkits for Aladdin 4D OS 4.0 version.
|
Posted on: 2007/12/27 19:42
#131
|
Just popping in
|
@Amigo1 IMHO, Feelin is very promising and offers new interesting features, the problem is that the API is still changing (faster than the builtin classes...) and the developer archive contains a significative amount of things "under construction". It has several advantages over MUI/ReAction (no BOOPSI, XML stuff, ...) but ATM I'm not sure you have the minimum required for the typical GUI (e.g. : no menus). Otherwise, it would be also a good candidate
|
|
|
|
Re: DiscreetFX is evaluating toolkits for Aladdin 4D OS 4.0 version.
|
Posted on: 2007/12/27 15:17
#132
|
Just popping in
|
@DiscreetFX I'll second for MUI, though I currently use ReAction for programming. If you plan to build versions for other systems this is the best choice, and besides that it has more high level features and classes than ReAction. Current OS4 version of MUI is way outdated and a bit buggy (vertical gradients, etc...), but I'm still hoping for a MUI4 port that would change the deal
|
|
|
|
Re: Memory protection and tasks/processes
|
Posted on: 2007/9/13 18:56
#133
|
Just popping in
|
@Hans
I mean DOS process, the parent/child feature is available through DOS function CreateNewProcTags().
|
|
|
|
Re: Memory protection and tasks/processes
|
Posted on: 2007/9/13 18:43
#134
|
Just popping in
|
@Hans
AFAIK, at the moment you'd better use MEMF_SHARED memory between your different processes because parent process memory flagged as MEMF_PRIVATE is not shared with its children (NP_Child flag) (someone correct me if I'm wrong).
|
|
|
|