Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Rich Walsh

Pages: 1 2 3 [4] 5 6 ... 23
46
Applications / Re: XWP v1.0.16
« on: December 27, 2023, 05:57:52 pm »
Do you think it can be possible to include a custom icon size for xcenter, (like the mock up attached picture) instead of just "small" and "large".

If I could have done so when I was working on it, then I would have. If things change someday and enable me to do so, then I will. But right now? No.

47
Applications / Re: DSSaver and XWP
« on: December 23, 2023, 04:42:11 am »
Should the "PRESPARAMS PP_FOREGROUNDCOLORINDEX, CLR_BLACK" lines also be deleted?

No, that just gives you black text rather than that wierd dark blue IBM liked.

I should be able to send you a late beta of my changes tomorrow. Attached is a screenshot of the rearranged Page 3. It's still big but all the pages fit the system-default notebook size.

48
Applications / Re: DSSaver and XWP
« on: December 23, 2023, 02:13:19 am »
Just remove the lines for PP_FONTNAMESIZE and PP_USER, save the file, and you're done.

Tried commenting those lines out, rc.exe was not happy. What does seem to work is removing the font size, s/10.System Proportional/System Proportional/g.
Have to consider changing the System Proportional to WarpSans as well. There's also buttons that need the same treatment.

I'm sorry to be difficult but none of the above is the correct way to handle this.

RC should accept /* */ comments but if it doesn't for some reason, just delete them as suggested (you can always have git revert any change). Further, generating defective entries just to get something kinda-maybe working is not helping your cause. Nor is substituting one hard-coded font for another when the goal of this exercise is to have dialogs comply with the user's choice of font & size.

Without those fonts entries, the dialog will use whatever font & size you've chosen - either because it has  inherited them from the dialog that created it (which is the way it should be), or because Styler has forced them to be system-compliant (turn off Styler's dialog enhancements to check).

Honestly, there's no need for any experimentation here - how this stuff works is fully known. If it doesn't work as it should, hacks and workarounds will only get in the way of finding the _real_ problem.

49
Applications / Re: DSSaver and XWP
« on: December 22, 2023, 05:54:02 pm »
Seems most of the modules have this in their RC files,
Code: [Select]
PRESPARAMS PP_FONTNAMESIZE, "10.System Proportional"
PRESPARAMS PP_USER, "12.System Proportional"

In the password stuff and the configure dialog. Have to play with the Universal Resource Editor (URE).

This is a job for a text editor, not a dialog editor. If you open the .RC file for each module, you'll find dialog templates like this one: Edit: but you already knew this
Code: [Select]
    DIALOG "Password protection", DLG_PASSWORDPROTECTION, 85, 62, 160, 45,
                FS_NOBYTEALIGN | FS_DLGBORDER | WS_CLIPSIBLINGS | WS_SAVEBITS,
                FCF_TITLEBAR | FCF_SYSMENU | FCF_CLOSEBUTTON
    PRESPARAMS PP_FOREGROUNDCOLORINDEX, CLR_BLACK
    PRESPARAMS PP_FONTNAMESIZE, "10.System Proportional"
    PRESPARAMS PP_USER, "10.System Proportional"
    BEGIN

Just remove the lines for PP_FONTNAMESIZE and PP_USER, save the file, and you're done.

Speaking of done... I'm almost done with the redesign of DSS's Desktop Properties pages. Each one is now a fixed size that fits the default dimensions of a Properties notebook. As a by-product of this effort, I was also able to lop off 1000 lines of code from the source - but it's still a bloated pig at a "mere" 4500 lines. Honestly, I've never seen so much effort expended on so little results. Another 1000-1500 lines could easily disappear and no one would ever notice...

BTW... Dave, could you PM me with your email address so I can send you some stuff?

50
Applications / Re: XWP v1.0.16
« on: December 18, 2023, 07:08:21 am »
I'm getting weird looking file sizes in the Xview folders

This also happens in conventional 'Details' view. The cause is believed to be code compiled using Open Watcom (e.g. DSS).

When files started to exceed 4gb, IBM had to come up with a way to display numbers greater than a 32-bit integer can handle. Rather than switching to 64-bit arithmetic (probably due to the compiler they were using), they opted to store the numbers in floating-point format. Converting a floating point number back to an integer requires that the machine's "floating-point control word" be set as the compiler expects. Unfortunately, OW-compiled code changes the control word's setting to suit its own needs, causing IBM C-compiled code to go haywire.

I added a fix somewhere in XWP to reset the control word back to the IBM standard just before the WPS displays a Details view window  - but clearly it doesn't work (or at least, doesn't work all of the time). The real solution is to have OW-compiled code that runs on Thread 1 (the WPS's UI thread) reset the control word appropriately.

This also means that it cannot do floating-point math on Thread 1 because its own results will be screwy (each thread has its own CW setting, so OW code can do whatever it wants on its own thread). This is one of several reasons I want to look at revising DSS's WPS notebook pages. (It's also one of the reasons I reject the notion of compiling WPS code with anything other than IBM VAC.)

51
Applications / Re: XWP v1.0.16
« on: December 18, 2023, 05:51:37 am »
In the System Setup folder, there is a folder called Extended Menu Options.
In the System Setup folder > XWP Installation folder, there is the XWPlace Configuration Folder.
Boh folders have the same object ID "<XWP_CONFIG>"

What you're seeing is a circular reference. Folder A contains a shadow of Folder B, which in turn contains a shadow of Folder A. Since shadows can have their own titles, distinct from the original, the circular reference may not be obvious. Feel free to rename stuff for consistency.

FWIW... the name "Extended Menu Options" came from ANXWP, the AN-branded XWP-Lite. Installing XWP-Full on top of it produced the shadow(s) of it named "XWorkPlace Configuration Folder".

52
Comments, Suggestions & Questions / Re: os2world website script problem?
« on: December 12, 2023, 07:18:43 pm »
it looks for a VGA compatible device when it loads and if it cannot find one, it outputs an error message and aborts. Maybe that is the way to test ...

Lars, the best way to test is to post the binary so people can test...  ;)

53
Applications / Re: XWP v1.0.16
« on: December 11, 2023, 06:17:19 pm »
having selected the MEDIUM size option I came to discover what I felt was a rather curious font/sizing choice for the default XWP menu, that being: '9. WarpSans Bold'. [...]  it feels (again, VERY subjective lol) like the [non-Bold] 10 pt is the better fitting size.

My overriding goal In implementing 'Text Size' was "user acceptance". Put another way, avoiding anything that would give people a reason for not using a feature that would clearly benefit them.

First and foremost in the list of things to avoid was any consideration of aesthetics. I fully agree with you that 'WarpSans Bold' at any size is a lousy font for menus. But, after all these years of people not complaining about it, it wasn't for me to go changing the status quo. By having Text Size use the exact same fonts that have been in place since eCS 1.0, no one can claim "aesthetic degradation" as a reason for not using it.

Quote
The 'Text Size' tab HELP states the following in relation to those using SNAP:
Quote
Note: if you use SNAP/Scitech Graphics, please remove any SET SDDFONTSIZE= or SET SDDFONTDPI= entries from 'config.sys' before rebooting to ensure expected results.
Can you elaborate further?

All of these SNAP and Panorama settings materially interfere with Text Size's operation by causing the system to choose the wrong default system font. Essentially, they were hacks to work around the lack of a comprehensive facility like Text Size. Further, they were added back in the days when 1024x768 was considered "high resolution" - they just don't have any relevance anymore, so don't set them.

54
Applications / Re: XWP v1.0.16
« on: December 11, 2023, 07:54:36 am »
Whenever I open the desktop properties and go to the Startup tab the delay always initially shows 1.  If I had previously changed it, I can hit Default and it will then show the number I had changed it to.

I had a quick look at this. If you set the value to say, 6, it will stay that way and the initial delay _will_ be 6 seconds - as long as you don't look at the Startup tab again. Displaying that tab is what resets the value to 1 (for as-yet unknown reasons).

If you want a safe way to confirm the setting is what you want, open an INI editor and look for XWorkplace->ulStartupInitialDelay. If present, its value is your chosen delay in milliseconds rendered in hex, If it's missing, then it has been reset to the default of 1 second.

I'll certainly get this fixed but it may be a while before the next release. When I have the makings of an initial beta that includes the fix I'll let you know.

55
Applications / Re: Re: XWP v1.0.16
« on: December 10, 2023, 05:35:23 pm »
can we get together and rearrange a few things so those pages aren't so crazy-big?

Here's what I would propose (and I'm willing to do the work to implement it if you wish):

Page 1 would be the current "General Settings" above and the "DPMS Settings" below (minus the excessive space between the checkboxes).

Page 2 would be "Password Protection". Note that this grouping by itself is nearly as tall as the tallest current n/b page (the View pages).

Page 3 would be the same contents just rearranged. Currently it's organized vertically but it would work better if it were layed-out horizontally: listbox and preview window side-by-side at the top, with the module info below. There are several possibilities for the locations of the checkbox and buttons, but it's hard to say what would look best until the major pieces are in place.

I think we'd probably agree that the whole "Module Information" group is far too large. The static text (now moved to the left of the MLE) could be condensed by removing the word "module". The "Supports password protection" line might be removed since every module supports it. Then too, you don't need the word "Description" - it's fairly obvious. And, of course, the MLE should be reduced to 3 or 4 lines max.

On the whole, I think this page's height could be made the same as the proposed Password page without looking at all cramped.The one thing I'd caution you against is feeling constrained by the way things are now. Just because the original author did something a particular way doesn't mean he did it _well_ - if he had, we wouldn't be having this discussion.

56
Applications / Re: XWP v1.0.16
« on: December 09, 2023, 10:28:59 pm »
Large parts of the XStartup code have been rewritten for improved reliability. It should no longer be necessary to impose a long delay to ensure the first object starts properly.
How hard would it be to add the initial delay back? I had imposed I think just a one second (maybe 3, I don't recall now) delay to prevent a 30-45 second hang that is now back (I had timed it back then but haven't now that it is back). 

I didn't get rid of the delay. It was a global rather than per-object setting, so I moved it to the Desktop 'Startup' tab where you create your first Startup folder. It starts out set to 1 second because there's always a 1-sec delay before XWP does _anything_. Values greater than 1 include that initial delay.

Quote
If the code is still there but just either commented or ifdef'd out, I should be able to build it (assuming my build environment is still good).

I seldom leave detritus lying around - that's what version-control systems are for. If there's a problem with any change I've made, please advise so that I can fix it for all users (assuming it needs fixing).

57
Programming / Re: Bigicons
« on: December 08, 2023, 09:17:18 pm »
David, I installed your 'BIGICONS_YELLOW' package and got a pleasant surprise when I opened some WPS folders and notebooks: XWP's window-list widget shows your icons rather than the originals. As expected, windows created by other apps retain their original icon.

Looking at 'bigicons.txt', I spotted these errors:
- the very first line is still missing. It should be "[SYSTEM]"
- lines 549 and 569 are supposed to be comments but they're missing the leading semicolon

If you're having problems with the size of the file (and you really shouldn't), there are two things you can do. As mentioned previously, if you don't supply an icon for something, get rid of its entry (e.g."WPSafeCapsule"). The other is to remove most of the comments. The cacheing system is very crude and does not remove them, so each time the app has to find something it has to plow through them. The fewer and the shorter, the better. I'd love to fix this stuff but it isn't my app and I don't have the rights to distribute it, so the best I can do is offer workarounds based on knowledge of the code.

BTW... you mentioned instability after restarting the WPS too many times. I was skeptical because there are days when I restart it 20-30 times in a session and have no problem. However, since working on this and my own Dynamic Icons-related project, I see what you mean. Yet another problem in need of fixin'...

58
Applications / Re: XWP v1.0.16
« on: December 08, 2023, 08:34:38 am »
I also noticed that "Comer Cursor" on the mouse settings does not respect the text size too.
Is Comet Cursor on XWorkplace, AMouse, or is old IBM code that can not be updated?

AOS replaces most of IBM's notebook pages with more attractive versions created by Alex Taylor. This looks like one of them. He's been working hard to get them all Text Size-compliant (and they should already be in 5.1) but he may have missed this one. I'll ask him about it.

FYI... I've been putting together a "Text Size Supplement" package that will make more WPS notebook pages work with Text Size. The most important component of the package is Alex's revised page layouts. This may not be needed for AOS 5.1 but all other release of OS/2 will benefit from installing them. Another component is a revised DTProgram DLL to make its Program object pages compliant as well. There may be other things included as well. The main hold up right now is finding time to write a custom installer (it's too complicated for WarpIn or RPM).

59
Comments, Suggestions & Questions / Re: os2world website script problem?
« on: December 07, 2023, 05:11:41 pm »
O.T....

Pete, where does that CPU meter in your screenshots come from? Is it a 3rd-party replacement or is it just so old I don't recognize it? (I rewrote "Pulse" 4 years ago in XWP 1.0.13.)

60
Programming / Re: Bigicons
« on: December 05, 2023, 05:25:12 am »
I found out that the bigicons.txt has a size limit before it destabilizes the entire wpshell.

I'd certainly be interested in looking at a copy of 'bigicons.txt' that was too big. I checked for obvious stuff (file buffer too small, memory allocated but not freed, etc) but nothing jumped out at me.

Pages: 1 2 3 [4] 5 6 ... 23