Messages

1

Nutcracker Effects / Re: Doing lyrics in a piecemeal approach

« on: October 14, 2018, 12:56:52 AM »

Ah great that makes sense!

So I should theoretically be able to add in timing marks coinciding with words, select those timing marks, change the label to the lyrics, then break it all down?

I’ll give that a shot because it sounds exactly like what I want to do!

2

Nutcracker Effects / Re: Doing lyrics in a piecemeal approach

« on: October 13, 2018, 01:16:00 AM »

It’s definitely possible. It’s how I do it


Sent from my iPhone using Tapatalk

Good to know! Could you share your “method” for adding to existing lyrics? Do you just use a new timing?

3

Nutcracker Effects / Doing lyrics in a piecemeal approach

« on: October 12, 2018, 11:29:19 PM »

Hi all,

I’m wondering if there’s an easy way to do the lyrics for faces using a piecemeal approach. To explain this, I’m planning on doing one section of lyrics, lining them up to the song, then breaking down the words. Once this is done, I’d then move on to the next section of the lyrics and to the same.

Is it possible to do this easily using one timing track? Or is a different timing track per lyric “section” the easiest approach? I’m also worried about any future updates to lyrics using this approach (I.e. we decide we want to do more lyrics for one section later on), as there doesn’t seem to be an easy way to retroactively add in lyrics, words and phrases.

Any ideas/advice on this?

Thanks!

4

Bugs in xLights/Nutcracker / Re: Arch Linux: Possible graphical bug?

« on: October 03, 2018, 05:12:58 PM »

I was trying to figure out why that ifdef was there as, like you said, the functionality in the switch statement doesn't seem like it would be broken without it because it's being done outside of wxWidgets

It likely should be an "#if !defined(__WXOSX__)"

On the Mac, the Copy/Cute/Paste is handled by those menu items on the main menu.   The accelerators kick in and call the appropriate methods.   Thus, without the ifdef, we ended up getting double pastes.

Just confirming this does indeed allow copy and paste to function properly on my machine (and I'm hoping it still allows OSX to work without doing a double copy, but I'll need to rely on someone with a Mac to test that).

Given this was your solution, did you want to do the commit for the change dkulp? Or do you want me to do a PR?

5

Bugs in xLights/Nutcracker / Re: Arch Linux: Possible graphical bug?

« on: October 03, 2018, 12:06:56 PM »

I was trying to figure out why that ifdef was there as, like you said, the functionality in the switch statement doesn't seem like it would be broken without it because it's being done outside of wxWidgets

It likely should be an "#if !defined(__WXOSX__)"

On the Mac, the Copy/Cute/Paste is handled by those menu items on the main menu.   The accelerators kick in and call the appropriate methods.   Thus, without the ifdef, we ended up getting double pastes.

Ahh ok that makes sense then! At least then it handles the case you mentioned without excluding everything else not using the Windows GUI controls

6

Bugs in xLights/Nutcracker / Re: Arch Linux: Possible graphical bug?

« on: October 03, 2018, 12:05:01 PM »

If would be best if you list filenames and line numbers when you start trying to describe a section of code.  When you say something like "the cases of the switch statement" I have no idea what code you are staring at.

Normally a copy/paste is done by clicking on the model's picture and not it's name in the list.  Which way are you trying to do it?  I'm just finding it hard to believe you are the first Linux user to ever try to copy a model.

Sorry in my eagerness I did leave some detail out. File in question is here: https://github.com/smeighan/xLights/blob/master/xLights/LayoutPanel.cpp and the ifdef I'm mentioning is on line 2838.

To copy, I'm simply clicking the model in the layout then ctrl+c and ctrl+v to paste

Certainly not suggesting this is more widespread, but possibly something to do with my machine not generating that preprocessor symbol during compilation, while other's machines are

7

Bugs in xLights/Nutcracker / Re: Arch Linux: Possible graphical bug?

« on: October 03, 2018, 11:22:56 AM »

I don't see where you mentioned exactly what you are trying to copy/paste.  I can tell you those wxWidgets docs probably have nothing to do with how our code works because we are capturing the keystrokes and executing copy/paste inside our code its not handled by wxWidgets.

The keystrokes are being handled yes, but part of that handling (including the copy paste functionality) is wrapped in that ifdef - and the preprocessor symbol it's look for (at least for me) isn't present. The cases of the switch statement that handle the copy paste don't even get hit because the symbol is missing. If I remove that ifdef for instance, it works properly (not saying this is the solution, but that it's definitely causing it to not work).

I was trying to figure out why that ifdef was there as, like you said, the functionality in the switch statement doesn't seem like it would be broken without it because it's being done outside of wxWidgets

8

Bugs in xLights/Nutcracker / Re: Arch Linux: Possible graphical bug?

« on: October 03, 2018, 11:16:54 AM »

Sorry - I'm doing the copy and paste in the layout view, not the sequencer. I'm attempting to copy and paste a model

9

Bugs in xLights/Nutcracker / Re: Arch Linux: Possible graphical bug?

« on: October 02, 2018, 05:30:04 PM »

OK so I think I've found the issue. The switch statement that is used to process the normal key bindings for copy and paste seems to depend on the preprocessor symbol __WXMSW__ being present - looking this up here: https://docs.wxwidgets.org/3.0/page_cppconst.html seems to suggest this will only be present when using Windows controls in the GUI - which I'm assuming won't be the case when using Linux?

I'm happy to fiddle with this and alter the code to handle my scenario (once I figure out what preprocessor symbol is actually present), then create a pull request if that helps?

10

Bugs in xLights/Nutcracker / Re: Arch Linux: Possible graphical bug?

« on: October 02, 2018, 02:19:18 PM »

Linux sure seems like a troublesome OS and when I tried it I found it a pain that every program you wanted to use you had to figure out if it was compatible with the 8000 versions of Linux.  I just don't get love for that OS.

Yep I can understand that view, some of us are masochists but to  be fair some things I’ve just found so much easier on a Linux box than windows - dev related setups especially

11

Bugs in xLights/Nutcracker / Re: Arch Linux: Possible graphical bug?

« on: October 01, 2018, 11:41:25 PM »

Ok finally got the depencies right on my machine to do the build successfully. After running the built binary, it seems to display the graphics fine, without having to use the dedicated graphics card.

Copy/Paste still isn't working, but I'm happy at least that the graphics seem to work properly now.

I do suspect this means there is something in the AppImage build process that my machine doesn't like. Finding out what that is might be the next step I suppose!

12

Bugs in xLights/Nutcracker / Re: Arch Linux: Possible graphical bug?

« on: October 01, 2018, 06:31:46 PM »

Copy and paste do not refer to the keybindings.


Sent from my iPhone using Tapatalk

Ok so potentially something related to the graphical issues I'm getting, given that seems to be specific to my setup. I think I’ll do a build and see if I get any joy, if I do then there must be something weird with the way the AppImage is packaged and my environment.

If not, then just my environment!

13

Bugs in xLights/Nutcracker / Re: Arch Linux: Possible graphical bug?

« on: October 01, 2018, 05:08:52 PM »

I don't know if it'll solve all your problems but try closing Xlights and then delete your key binding file from your show folder then reopen Xlights.

Did you try this advice?

Sorry just realised I didn't explicitly state that - yes I did remove the bindings xml file. So my timings seem to be working properly now, just not copy/paste. I'll keep looking and see if there's any obvious reason why that is though

14

Bugs in xLights/Nutcracker / Re: Arch Linux: Possible graphical bug?

« on: October 01, 2018, 04:04:31 PM »

Hitting T never does anything you gotta hit t.

Problem solved!

But in all seriousness, I hadn't thought of that! Alas my shortcuts don't seem to be working still - some seem to work (like the function keys) but copy/paste and timing marks still seem to be doing nothing.

Perhaps I should build from the repo and see if I get any joy running directly from there...

EDIT: Timing marks seem to be working properly now! Now to figure out why it refuses to copy/paste...

15

Bugs in xLights/Nutcracker / Re: Arch Linux: Possible graphical bug?

« on: October 01, 2018, 05:39:30 AM »

OK I might have spoken too soon...I don't seem to be able to use any keyboard shortcut (ctrl c and v for copy and paste for instance), and as a result I can't manually add timing marks - hitting T does nothing when running a sequence.

Any ideas?