Recent Posts

Pages: 1 [2] 3 4 ... 10
11
Applications / Re: LarsenCommander - new test version
« Last post by Rich Walsh on April 22, 2024, 10:29:43 pm »
I would like to have something that saves me some time grabbing by default font size (as XWP shows as default), but I understand that it is not easy to implement for each component described in the Font settings of lcmd.

It shouldn't be particularly hard: there are 5 entries under 'os2.ini->PM_SystemFonts'  [see below] and you map them to your categories. For example, 'PM_SystemFonts->Menus' maps to lcmd's 'AppWin.MenuBar' and its other menu settings.

DefaultFont: System Proportional - if this entry is missing/empty, assume 10 point SysPro

IconText:  WarpSans - this is mislabelled, it should be "Folder text" since it also is used for Details view
WindowText: WarpSans - standard dialog text

Menus: WarpSans Bold - both menubars and popups
WindowTitles:  WarpSans Bold

The key to using defaults while still allowing customization is *never* save the default value. That way you don't get stuck with a value that _used_ to be the default but isn't any longer.
12
Comments, Suggestions & Questions / Re: Hobbes (Files) Reoganization
« Last post by Martin Iturbide on April 22, 2024, 09:40:56 pm »
Hello

At the end Nathan accepted the changes and now we have a directory for Win16 and a different one for Win32.

I would like to eventually populate that directories with software tested on Win-OS2 and Odin under ArcaOS, but I think I will request some help on a different thread.

For now, I think I'm done withe Hobbes directory structure, I don't see any other idea on this area.

I guess the strategy now will be to find and upload any OS/2 Freeware/Shareware/Open Source/Public files that may be missing on the site. 

Any other suggestions for Hobbes Archive are welcome and I will check them out with Nathan.

Regards
13
Applications / Re: LarsenCommander - new test version
« Last post by Martin Iturbide on April 22, 2024, 06:33:59 pm »
Hi
Does this not work for your on one of the controls?

Though I for myself rarely had the need to change my fonts the last decade or so as I still use monitors with 94-105dpi (most of the time).
Yes, it works for me with the usual way of changing the fonts with "Font Palette". But In my case I would like to adjust the font size a little bit bigger. I would like to have something that saves me some time grabbing by default font size (as XWP shows as default), but I understand that it is not easy to implement for each component described in the Font settings of lcmd.

Regards
14
Programming / Re: Dive: Why does not this work
« Last post by Dave Yeo on April 22, 2024, 05:26:38 pm »
I wonder then, how SDL work then. There is not one mention of WM_VRN*. It just blits the whole SDL surface to the buffer (no direct VRAM access).

Cairo does the same. A comment in the code,
Code: [Select]
* This function uses DIVE to write those portions of the surface identified
* by @rect directly to the screen buffer.  It only supports 32- or 24-bit
* full-color video modes.  To avoid painting overlapping or child windows,
* it must perform all of the visible-region calculations that GPI normally
* handles.  Despite this, it provides a significant improvement in speed
* compared to using GPI functions.
15
General Discussion / Re: PMfax
« Last post by nyao on April 22, 2024, 05:02:25 pm »
Hi.
A precautionary note from when I installed it a long time ago.
It is unknown whether it is related to imgfx6mn.dll.

"Please note that if you do not enter the registration key from Add.exe after installation (maybe the procedure is incorrect?), the program will not start and will only display a message recommending that you contact the company."
http://hp.vector.co.jp/authors/VA028575/faq.htm#32
16
Programming / Re: PMPrintf package v2.80 and PMPrintf_abtrace code samples
« Last post by Martin Iturbide on April 22, 2024, 03:50:08 pm »
Thanks Andi B.

I had also uploaded it to HobbesArchive.com to have it as backup too.

Regards
17
Programming / Re: Dive: Why does not this work
« Last post by Jochen Schäfer on April 22, 2024, 12:35:44 pm »
I wonder then, how SDL work then. There is not one mention of WM_VRN*. It just blits the whole SDL surface to the buffer (no direct VRAM access).
18
Programming / Re: Dive: Why does not this work
« Last post by Lars on April 22, 2024, 12:27:08 pm »
The samples seem to indicate that you are forbidden to drive screen updates in between calls WM_VRNDISABLED and WM_VRNENABLED. That is, there is a timespan where you are not allowed to blit anything to the screen, that means, the Classicube draw buffer function should do nothing during that timespan.
That in turn means, the proper point in time to call DiveSetupBlitter are WM_VRNDISABLED and WM_VRNENABLED. The "Remarks" section for DiveSetupBlitter even states that DiveSetupBlitter is "not intended to be called at high frequency".

This would be even more relevant for direct screen updates (that is, if you used DiveAcquireFrameBuffer / DiveDeacquireFrameBuffer / DiveSwitchBank / DiveCalcFrameBufferAddress and direct writes to the video aperture "ppFrameBuffer" as returned by DiveOpen) but for already mentioned reasons you should not do that anyways.

Still, it looks as if DIVE still needs to be notified via DiveSetupBlitter when WM_VRNDISABLED and WM_VRNENABLED are called for a specific window even if you do not do direct screen updates.
19
Programming / Re: Dive: Why does not this work
« Last post by Jochen Schäfer on April 22, 2024, 11:33:25 am »
I understand that, but Classicube calls the draw buffer function with a rectangle to paint, so I setup the blitter in the draw function. This should work I would think.
20
Programming / Re: Dive: Why does not this work
« Last post by Lars on April 22, 2024, 11:23:35 am »
Look at the OS/2 toolkit, in the "beehive" sample code (in that code you can ignore everything that centers around sprite creation. You can also ignore everything that centers around full screen DIVE unless you really want to do that, that includes loading GAMESVR [deprecated since Warp 4] or PMMERGE  Dive Fullscreen Init procedure).

I think you will need to support the WM_VRNDISABLED and WM_VRNENABLED window messages and use DiveAllocImageBuffer,DiveBlitImage,DivFreeImageBuffer. Note that the sample does the blitting from a secondary thread.
Yes, I do use the Dive functions, but WM_VRNDISABLED AND WM_VRNENABLED are not much use for me, since Classicube gives me the rectangles it wants to paint to, anyway. Moreover, SDL2 works without using the window messages, so it seems optional.

Look at the help for the "DiveSetupBlitter" function. You need to support WM_VRNDISABLED and WM_VRNENABLED in order to notify the Dive Blitter via "DiveSetupBlitter" that changes to the visible regions will start or end to occur.
On a reception of WM_VRNDISABLED you need to disable the blitter, on a reception of WM_VRNENABLED you will need to set up again the blitter with the proper values.
Pages: 1 [2] 3 4 ... 10