|
|||||||
|
|
|
|||||
|
|
|||||||
get_pci_info?TextView) use a fixed font?libatheos methods, like Desktop().GetResolution()?#atheos, on any ircnet server (e.g. irc.stealth.net, irc.belwue.de, irc.leo.org, irc.fu-berlin.de)get_pci_info?
Characters above the 7-bit ascii range must be typed as UTF-8 encoded multichars in hex, e.g. the Norwegian "aa" is encoded as the two-byte UTF-8 character(0xc3,0xa5). This gets encoded as 0xc3a5 in the ascii keymap file.
[Back to top]
/tmp/snapshot.png"
TextView) use a fixed font?pcTextView is your TextView object, and Lucida Sans Typewriter is your monospace typeface here's an example for release 0.3.2,
// Change the font
Font* pcAppFont = new Font ( *pcTextView->GetEditor()->GetFont() );
pcAppFont->SetFamilyAndStyle( "Lucida Sans Typewriter", "Regular" );
pcTextView->GetEditor()->SetFont(pcAppFont);
There were some improvements made to font-handling in release 0.3.3. Font's are now reference-counted - this makes it easier to share font's between views. The notification system now allows a view to keep track of any changes made to it's current font (including replacing the font). The os::TextView class now listens to those notification's and applies the changes to its internal text-editor, so if you change os::TextView's font, internal editor will also reflect the change.
[Back to top]
libatheos methods, like Desktop().GetResolution()?os::Application class created, and running (os::Application::Run()) before you make any calls to things like Desktop().GetResolution().
os::Bitmap class. Xspringies use a bitmap for "double-buffering" and use the appserver to render into it (by adding a view to the bitmap). IconEdit and bmview copy bitmap-data into the bitmaps themselves and only ask the appserver to render the finished bitmap into an on-screen view. Desktop-manager does both.
os::Bitmap::LockRaster() member. You can then copy the pixel data directly to that buffer.memcpy( pcBitmap->LockRaster(), pBitmapData, nBitmapSize );
LockRaster() that returns the pointer and a method named UnlockRaster() that releases it. The application server needs the lock/unlock mechanism to know when it's safe to move the bitmap, if the video-memory it uses is needed by someone else.Lock() and Unlock() member that will protect the Bitmap object locally by acquiring a semaphore, and notify the application server so it doesn't move the bitmap between Lock() and Unlock() operations. The LockRaster() and UnlockRaster() will then be removed and a GetRaster() will be added instead. The above example will then look like this:pcBitmap->Lock();
memcpy( pcBitmap->GetkRaster(), pBitmapData, nBitmapSize );
pcBitmap->Unlock();
os::Bitmap::LockRaster() so you can copy your bitmap-data into the bitmap (see previous answer). Remember to set the os::Bitmap::SHARE_FRAMEBUFFER flag when constructing the bitmap or else os::Bitmap::LockRaster() will always return a NULL pointer.