[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
I had posted a request on seeing how many cores a system had. Is that
in Allegro5 already or not? Also, what part of the system would that
function go? I'm guess threads.
On Wed, Mar 24, 2010 at 12:35 PM, Evert Glebbeek <eglebbk@xxxxxxxxxx> wrote:
> On 24 Mar 2010, at 11:53 , Elias Pschernig wrote:
>> One feature I think we still need:
>>
>> - Capabilities querying API. Among others it should report:
>>
>> ALLEGRO_HAVE_SET_BITMAP_TARGET
>>
>> If this is not available, al_set_target_bitmap cannot be (reasonably) used except for using our software rasterizer for drawing to memory bitmaps.
>>
>> ALLEGRO_HAVE_SET_SEPARATE_ALPHA_BLENDER
>>
>> If this is not available, al_set_separate_blender cannot be used (it will just ignore the alpha values passed in and work like al_set_blender otherwise).
>
> Ok.
> Shouldn't be hard to add, right?
>
>> Dario (I think) seems to have hit a stumbling block with enabling texture stages or something. It would be really nice to have of course, but we could release 5.0 without it.
>
> I think we can import it without that and worry about it after that.
> Ok, so it'a not bug-free. If we let it sit, it'll just bit-rot.
> Or we take the position that it should be a separate addon.
>
>> * MAXIMISED_WINDOW flag?
>>
>> Should be simple to do in X11. My use case is if I exit my level editor while maximized, I'd like it to start maximized again the next time - but didn't get to work on my editor for some time hence the feature was not added either :P
>
> Equally simple on OS X, but I don't have time to go and add it for anything else.
>
>> It's just hard to do because it depends so much on the driver. With the nvidia drivers on my setup at home FULLSCREEN_WINDOW is the only viable solution as non-native resolutions use crappy scaling built into the monitor and the gfx card can do much better scaling for free with native resolution.
>
> That's not a good excuse. :P
>
>> Fullscreen windows can never fail in X11 (Allegro itself chooses the size after all) and I'd hope the same is true for Windows.
>
> That's nice, but it's not true on OS X. Hence why I asked.
>
>> While I kinda don't like a feature freeze, I know that it's necessary if we ever want to get 5.0 out.
>
> :P
>
>> Feature freeze after next WIP sounds good to me.
>
> Ok.
>
> Evert
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> --
> https://lists.sourceforge.net/lists/listinfo/alleg-developers
>
--
Note: No trees were killed in the sending of this message, but a large
number of electrons were terribly inconvenienced.