XWP v1.0.16

[Rich Walsh]

This sub-thread is yet another good reason to use XWP-Lite/ANXWP: it comes preconfigured.

In XWP-Full, you need to check "XWorkplace Installation->XWorkplace Setup->Features->Mouse and Keyboard features->Enable global object hotkeys"

[Martin Iturbide]

This sub-thread is yet another good reason to use XWP-Lite/ANXWP: it comes preconfigured.

In XWP-Full, you need to check "XWorkplace Installation->XWorkplace Setup->Features->Mouse and Keyboard features->Enable global object hotkeys"

Thanks Rich. That was what I needed. XWP full does not enable by default the "Enable global object hotkeys". Now the hotkeys works fine.

Regards

[Pete]

I do not have Dynamic Icons installed as, quite simply, it is broken.

How, exactly, is it broken (vs. merely deficient)? I've been using it for 6+ years and it WFM. There's a new version awaiting release that fixes most of the problems I found and uses a lot less memory. Hopefully it will work for you.

Errmm.. A reply from yourself in the Bigicons discussion

In this case, the problem is not operator error or a bad install - it's just broken. I can reliably lock up my system by using D&D to copy a program object to a folder that's open in Icon view. You might think that I would have noticed this before but I use Xview almost exclusively and only have 2 folders that use Icon view (one of them being the Desktop).

Looking forward to trying the new release in the near future.


Regards

Pete

[Rich Walsh]

XWP full does not enable by default the "Enable global object hotkeys".

I made the mistake of assuming it did, and that the settings on the Icon page would be disabled if the feature were disabled - neither of which was true. I've now fixed both.

In doing so, I found a bigger issue: XWP-Full starts with fewer features enabled than XWP-Lite/ANXWP. Since nothing in Lite is risky/experimental/controversial, I can't see any reason why Full shouldn't default to the same feature set as Lite. In the next version (1.0.17), it will. All the checkboxes will remain, only the ones that are checked by default will change.

BTW... this only affects new installations - upgrades will use your existing settings and shouldn't change anything.

[Pete]

Hi Rich

The joy of the full version is (used to be?) that it starts with no features enabled and the user selects what they want.

I guess in future the user will simply have to select what they want and deselect anything they do not want...


Regards

Pete

[Martin Iturbide]

Hello

I created this ticket, about enhancing XWPKeyboard Mappings.

http://trac.netlabs.org/xworkplace/ticket/11

I think it can be interesting to grab the idea of "Folder Hotkeys" and put it on "Mappings" so different combination of keys can be assigned to some desktop actions (parameters).
But I guess it will be more interesting if more "desktop actions" can be added to XWP there, like the ones in "Windows Keys" like "Hide/show all windows", "Show windows list", "Lock up desktop", etc. 

Regards

[Dariusz Piatkowski]

Rich,

New feature request: would you consider implementing BLDLEVEL file object pop-up functionality?

What I'm envisioning is the ability to right click on a DLL, or any object that does contain the BLDLEVEL information, and have this stuff either pop-up directly under some sort of 'Version' or 'BldLevel' menu entry, or perhaps another place such as under 'Properties'

[Martin Iturbide]

Hello Dariusz

I think that XWPProgramFile Class (or is it some other WPS Class?) has already something implemented (See picture) on the "Module" tab. But I have no idea how to have the same information for DLLs files.
What it would be great too, it to have a way to Ctrl+C that information.

Regards

[Martin Iturbide]

But I have no idea how to have the same information for DLLs files.

I was able to also have the "Module" tab on the DLLs by using Rich's improved OO and the procedure from this forum thread.
I changed all the DLLs on C:\OS2\DLL to XWPProgramFile

Regards

[Dariusz Piatkowski]

Hello Martin,

...I think that XWPProgramFile Class (or is it some other WPS Class?) has already something implemented (See picture) on the "Module" tab. But I have no idea how to have the same information for DLLs files...

Hmm...so for some reason I do not see this being populated for some EXEs, such as the NewView.exe, where at CLI there certainly is BLDLEVEL info showing.

DLL wise, turns out that not all DLLs are classified as XWPProgramFile object, which is perhaps why so it happened that the DLLs I was looking at showed no such Module tab.

So at a follow-up, two actually, I'm curious:
1) DLL object type conversion
- reading that other thread you shared, it seems like this was a manual process that needed to be done for every new DLL, is that correct?

2) re: XWP NEW Feature request: now that I understand what's already there (or should be there), I would like to just stick to the menu selection which would simply show that BLDLEVEL info in it's own pop-up

[Martin Iturbide]

Hi

1) DLL object type conversion
- reading that other thread you shared, it seems like this was a manual process that needed to be done for every new DLL, is that correct?

I did the manual process of converting the DLLs from "WPDataFile" to "XWPProgramFile" using Rich's newer OO and creating a CMD according to his suggestion. The .CMD only works for directories, maybe some more tweaking can be done in REXX to create something that change all files in subfolders.

DLL2Prog.CMD
------------------
oo /+
for %%1 in (*.dll) do oo /B %%1 XWPProgramFile
oo /-
------------------

[Rich Walsh]

I would like to just stick to the menu selection which would simply show that BLDLEVEL info in it's own pop-up

Why wait for someone to implement a feature that you can have _now_?

Open Properties for \os2\bldlevel.exe, and on the 'Session' page uncheck "Close window on exit". Then on the 'Association' page, add "*.DLL" and "*.EXE". Done! When you need this info, select 'Open as', then 'bldlevel.exe'.

FWIW... on my system, any info I may need about a binary is immediately at hand because I have associated 6 different utils with *.exe and *.dll. Some of these associations are program objects while others point at the exe itself:
unlock.exe
exehdr.exe
exeinfo.exe
pmdll.exe
hexedit2.exe
bldlevel.exe

Warning: you can *not* copy/paste from a VIO window whose app has terminated - it's instant death. If you need this ability, associate a simple .cmd file like this and leave "Close window on exit" checked:

-----bldlvl.cmd-----
@bldlevel %1
@pause
------------------------

[Martin Iturbide]

Hello

I'm just writing down which other software does not respect "adhere to" the default font size that can now be controlled with the XWP "Font Size" feature.
- WarpIn
- ArcaOS Package Manager
- NewView (Works fine on 2.19.9)
- (kLIBC) User Manager
- DragText
- Extended Character  Map
- Lucide
- PMDCalc Plus
- Remote Desktop Connections

Regards

[Alex Taylor]

I'm just writing down which other software does not respect the default font size that can now be controlled with the XWP "Font Size" feature.
- ArcaOS Package Manager
- NewView

A distinction needs to be made here between "respect" and "adhere to".  These programs have their own user-customizable font size setting which they use in preference to any others. This is as it should be. 

In fact, NewView does use the system font setting as its default if (and only if) a user font is not specified. Again, this is as it should be.  Of course, this normally happens only when you first run it after a fresh install. Try deleting newview.ini and then see what happens. 

[Martin Iturbide]

A distinction needs to be made here between "respect" and "adhere to".  These programs have their own user-customizable font size setting which they use in preference to any others. This is as it should be. 

Thanks Alex for the correction, the right word should be "adhere to", since "respect" may sound aggressive, like if the software is "disrespecting" something and that is not what I mean.  Thanks for helping me find the right word.

Also the idea is not to force or lock the font size of style of the software, it is just to start with the default and let the user change their font style and size if he wants to, like it has always been possible on OS/2. It is always the choice of the developer what font to use, but the idea is just to give a convenience to the user to be able to change the size of all the fonts at once now that XWP has that feature.

Regards