LS programming help please :)
Sunday, October 3, 2004 by werewolf | Discussion: WinCustomize Talk
I am trying to do something which seems to be very simple: Click the Middle mouse button and display a list of desktops from the vwm.
There is a theme, fo-src, which does this. I have looked at every .rc file I could find and I have tried the following in my theme:
I have jdesk.rc which contains the following:
jdeskworkarea "0,25,1280,974" !haven't figured out how the negative number thing works yet
*jDeskMButton3 [CTRL!none!ToggleCommand!none] << THIS WORKS
*jDeskMButton3 [!none!none!popupvwm!none]
I have popupvwm.rc which contains the following copied from the fo-src theme:
If VWM TRUE
*Popup "" !New !Popupvwm
*Popup "Desktop 1" !VWMDesk 1
*Popup "Desktop 2" !VWMDesk 2
*Popup "Desktop 3" !VWMDesk 3
*Popup "Desktop 4" !VWMDesk 4
*Popup ~New
ENDIF
I have these two entries in my theme.rc file:
include "$configDir$jdesk.rc"
include "$configDir$popupvwm.rc"
I really don't know what else to do to get this to work. I've looked through the docs for the vwm module and the jdesk module, but I can't find any docs which state "if you want to do something like this, you have to have this/these .rc file(s) and you have to make entries in these .rc files and you have to set up these themevars...."
jdesk-0.711
popup2-2.1.4
ckvwm-1.40
Thanks so much. This isn't as easy as AstonShell

David
Reply #22 Sunday, October 3, 2004 10:45 PM

Reply #23 Sunday, October 3, 2004 10:46 PM

Reply #24 Sunday, October 3, 2004 10:47 PM
Reply #25 Sunday, October 3, 2004 10:50 PM
Reply #26 Sunday, October 3, 2004 10:51 PM
Reply #27 Sunday, October 3, 2004 10:59 PM
Reply #28 Monday, October 4, 2004 12:03 AM
Reply #29 Monday, October 4, 2004 12:34 AM
I thought you wanted to do something 'sexy' with the popup...but it's just a vwm switcher....shouldn't be that hard to set....I'll have to check what you've done to make it not work....
Strangely I don't get the hotkey errors on my Antares...though others have done so.....easy enough just to comment out the hotkey and ignore it...
Reply #30 Monday, October 4, 2004 9:02 AM
Here....
add this to the end of theme.rc in Antares II and you'll have it working in mine....
*Popup "" !New !Popupvwm
*Popup "Desktop 1" !VWMDesk 0
*Popup "Desktop 2" !VWMDesk 1
*Popup "Desktop 3" !VWMDesk 2
*Popup "Desktop 4" !VWMDesk 3
*Popup ~New
*Desktop MButton+SHIFT !Popupvwm
[Message Edited]
Reply #31 Monday, October 4, 2004 9:07 AM

Reply #32 Monday, October 4, 2004 9:26 AM
Actually....23 resource files is just asking for trouble.
I'm sure there's better ways than that to handle options....
Reply #33 Monday, October 4, 2004 6:34 PM

I'm modifying the default theme which comes with Omar's installer called austerity. I haven't touched the personal theme (well, actually, I did and I didn't back it up first and well, there's a line which says "don't mess with this unless you know what you are doing". Hee hee. See to me, that just means I gotta break it and I did! So I reinstalled LS...but that's another story. I'll poke around for conflicts, but I didn't see any other popup calls from jdesk or anywhere else other than the regular two.
OK, I put the popupvwm in the bottom of the theme.rc file and got rid of popupvwm.rc. No joy.
Issuing !vwmdesk 1 in lsxcommand works great. hmmm...must eat...brb

Reply #34 Monday, October 4, 2004 7:54 PM
Reply #35 Monday, October 4, 2004 8:44 PM
Reply #36 Monday, October 4, 2004 8:48 PM
Mouse actions for jdesk and desktop modules give you multiple settings to each mouse/keyboard control.
It's possible to have two lines trying to run the same 'action' in two different rc files causing conflict.
The theme you initially asked about has conditional statements as well linked to the vwm....so a separate 'config' again may actually disable the vwm function totally.
Reply #37 Monday, October 4, 2004 8:51 PM
jDeskDisableMButton1
  - If set, all jDesk Mouse Button 1 functionality
    is disabled.
  - boolean value: true if set, otherwise false.
jDeskDisableMButton2
  - If set, all jDesk Mouse Button 2 functionality
    is disabled.
  - boolean value: true if set, otherwise false.
jDeskDisableMButton3
  - If set, all jDesk Mouse Button 3 functionality
    is disabled.
  - boolean value: true if set, otherwise false.
jDeskDisableMButtonX1
  - If set, all jDesk Mouse Button X1 functionality
    is disabled.
  - boolean value: true if set, otherwise false.
jDeskDisableMButtonX2
  - If set, all jDesk Mouse Button X2 functionality
    is disabled.
  - boolean value: true if set, otherwise false.
jDeskDisableMWheelScroll
  - If set, all jDesk Mouse Wheel Scroll
    functionality is disabled.
  - boolean value: true if set, otherwise false.
jDeskDisableDoubleClick
  - If set, all jDesk ignores Double Click actions and
    immediately executes the up action command instead
    of waiting to see if a double click is being
    executed.
  - boolean value: true if set, otherwise false.
*jDeskMButton1
  - parameters:
    [<modkey><down-cmd><up-cmd><dblclick-cmd>]
    <modkey> can be one of the following
      SHIFT
      CTRL
      CTRL+SHIFT
    <down-cmd>
    <up-cmd>
    <dblclick-cmd>
      can be any !Bang command or executable that
      is to be executed.
  - Multiple settings of this definition are
    allowed, but only one definition using the same
    modkey is allowed.
  - If no definitions are specified, Button is
    disabled.
*jDeskMButton2
  - parameters:
    [<modkey><down-cmd><up-cmd><dblclick-cmd>]
    <modkey> can be one of the following
      SHIFT
      CTRL
      CTRL+SHIFT
    <down-cmd>
    <up-cmd>
    <dblclick-cmd>
      can be any !Bang command or executable that
      is to be executed.
  - Multiple settings of this definition are
    allowed, but only one definition using the same
    modkey is allowed.
  - If no definitions are specified, Button is
    disabled.
*jDeskMButton3
  - parameters:
    [<modkey><down-cmd><up-cmd><dblclick-cmd>]
    <modkey> can be one of the following
      SHIFT
      CTRL
      CTRL+SHIFT
    <down-cmd>
    <up-cmd>
    <dblclick-cmd>
      can be any !Bang command or executable that
      is to be executed.
  - Multiple settings of this definition are
    allowed, but only one definition using the same
    modkey is allowed.
  - If no definitions are specified, Button is
    disabled.
*jDeskMButtonX1
  - parameters:
    [<modkey><down-cmd><up-cmd><dblclick-cmd>]
    <modkey> can be one of the following
      SHIFT
      CTRL
      CTRL+SHIFT
    <down-cmd>
    <up-cmd>
    <dblclick-cmd>
      can be any !Bang command or executable that
      is to be executed.
  - Multiple settings of this definition are
    allowed, but only one definition using the same
    modkey is allowed.
  - If no definitions are specified, Button is
    disabled.
*jDeskMButtonX2
  - parameters:
    [<modkey><down-cmd><up-cmd><dblclick-cmd>]
    <modkey> can be one of the following
      SHIFT
      CTRL
      CTRL+SHIFT
    <down-cmd>
    <up-cmd>
    <dblclick-cmd>
      can be any !Bang command or executable that
      is to be executed.
  - Multiple settings of this definition are
    allowed, but only one definition using the same
    modkey is allowed.
  - If no definitions are specified, Button is
    disabled.
*jDeskMWheelScroll
  - parameters:
    [<modkey><down-cmd><up-cmd>]
    <modkey> can be one of the following
      SHIFT
      CTRL
      CTRL+SHIFT
    <down-cmd>
    <up-cmd>
      can be any !Bang command or executable that
      is to be executed.
  - Multiple settings of this definition are
    allowed, but only one definition using the same
    modkey is allowed.
  - If no definitions are specified, Wheel Scroll
    is disabled.
 
Reply #39 Monday, October 4, 2004 9:29 PM

Reply #40 Monday, October 4, 2004 9:39 PM
When using Omar's installer (and it is probably the best, certainly the most commonly used distro of litestep) each theme needs to contain a "theme.rc". You can contain all the litestep commands, parameters, etc in that one file. I have many themes that do just that.
But if you look at "austerity" as an example, you can have a theme.rc and have it point to many other rc's (usually an rc per module config).
Both systems work. In theory more rc's might take slightly longer to load at a reboot or recycle (but the difference is real slight).
Having multiple rc's makes it easier to have problems like conflicting (multiple) lines. But seperating module commands into seperate rc's makes it easier for some people to follow. I have used this method in themes as well, works good too.
Also keep in mind that there are rc files external of any given theme, that are loaded by default with all themes (personal.rc, hotkey.rc, popup.rc, evars.rc). You have probably already discovered these

Please login to comment and/or vote for this skin.
Welcome Guest! Please take the time to register with us.
There are many great features available to you once you register, including:
- Richer content, access to many features that are disabled for guests like commenting on the forums and downloading skins.
- Access to a great community, with a massive database of many, many areas of interest.
- Access to contests & subscription offers like exclusive emails.
- It's simple, and FREE!







Reply #21 Sunday, October 3, 2004 10:43 PM
I like the doohickey, that's pretty clever. Will have to see how you did that.
There's a little panel which reveals itself on mouse over down and to the left of the 'fan'. I can't read it, my zoomer apps can't see it, clicking on it doesn't do anything. What is it?
[Message Edited]