Author Topic: Arch Linux: Possible graphical bug?  (Read 2242 times)

Offline olorin92

  • Newbie
  • *
  • Posts: 24
    • View Profile
Re: Arch Linux: Possible graphical bug?
« Reply #30 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
« Last Edit: October 03, 2018, 12:08:02 PM by olorin92 »

Offline olorin92

  • Newbie
  • *
  • Posts: 24
    • View Profile
Re: Arch Linux: Possible graphical bug?
« Reply #31 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
« Last Edit: October 03, 2018, 12:09:09 PM by olorin92 »

Offline Gilrock

  • Supporting Member
  • Hero Member
  • *
  • Posts: 6946
    • View Profile
Re: Arch Linux: Possible graphical bug?
« Reply #32 on: October 03, 2018, 01:46:19 PM »
Ok thanks.  I'm not at home so I wasn't able to browse the code very easily.  I can look online on GitHub but its not as easy as what I can do at home.  You had me thinking you were looking at a #ifdef inside wxWidgets.  Sounds like Dan's suggestion is the way to go.

Offline olorin92

  • Newbie
  • *
  • Posts: 24
    • View Profile
Re: Arch Linux: Possible graphical bug?
« Reply #33 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?

Offline debenham

  • Jr. Member
  • **
  • Posts: 59
    • View Profile
Re: Arch Linux: Possible graphical bug?
« Reply #34 on: October 04, 2018, 12:21:14 AM »
BTW - regarding the original gui bug - the appimage includes a number of libraries and so as part of its running it sets up library paths etc.  The problem with dual-vendor GPU systems (ie onboard graphics + nvidia GPU) is that there is a bunch of trickery done to get the right GL stuff loaded which is likely getting messed up/confused by appimage.