Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » U++ Library support » U++ Core » [FEATURE REQUEST] could Alloc fail a little more gracefully?
Re: [FEATURE REQUEST] could Alloc fail a little more gracefully? [message #17808 is a reply to message #17706] Fri, 29 August 2008 19:52 Go to previous messageGo to previous message
amrein is currently offline  amrein
Messages: 278
Registered: August 2008
Location: France
Experienced Member
nixnixnix wrote on Wed, 27 August 2008 01:49

Because of the data types my app handles, it really isn't practical to run it with less than 2GB RAM and preferably 4GB and probably a dual or quad core machine (in fact a lot of my users are on dual quad core CPUs with 4 GB or more). Even with my super small grid2d objects instead of 2d arrays, I am still going to get people crashing through the 2GB 32 bit memory limit so the idea that an image over 100MB is unwieldy does not apply in this case.

Is there a way that UPP users could setup their app for their chosen maximum image size?

Nick



If you mean "How can I know the image size in memory or image x,y,dx,dy attributes before loading it?" then I think the short answer is you can't at present. If you want to know the file size on disk before loading it then you can use GetSize() from FileIn.
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: StrIntValue -> uses int64
Next Topic: Full Support for timezone/DST [FEATURE REQUEST]
Goto Forum:
  


Current Time: Sun Jul 20 01:04:27 CEST 2025

Total time taken to generate the page: 0.04703 seconds