Cockos Incorporated Forums

Cockos Incorporated Forums (https://forum.cockos.com/index.php)
-   WDL users forum (https://forum.cockos.com/forumdisplay.php?f=32)
-   -   Starting SWS GUI config (https://forum.cockos.com/showthread.php?t=211276)

Dizzee 09-18-2018 07:29 AM

Starting SWS GUI config
 
Hello,

I am trying to change the GUI of the Notes in the SWS extensions but i'm struggling to start as i have never used XCode or haven't programmed in a while. I do know how to read the code. Can anyone suggest me where can i start please? When i used to work with visual studio i remember i had the design view and then the code behind. I am struggling a bit on finding the same design view on XCode.

Thank you

Xenakios 09-18-2018 08:00 AM

As far as I know, you won't be able to do it visually in XCode. (You could maybe attempt to edit the .rc files manually in a text editor, though.)

The GUI resources for Reaper and Reaper extensions are supposed to be done on Windows in Visual Studio, and for OS-X they are translated from the Microsoft resource files into C++ code with the PHP script (mac_resgen.php) that is included in the WDL/SWELL source tree.

Dizzee 09-18-2018 08:41 AM

Quote:

Originally Posted by Xenakios (Post 2036118)
(You could maybe attempt to edit the .rc files manually in a text editor, though.)

The issue is that i want to add icons on the notes window that link back to actions on reaper main window. It would be a bit hard to position them just through the code no? visually i could just place them and in the back code link them

Dizzee 10-10-2018 07:50 AM

I am having another issue that is, my extensions project is not identifiyng the WDL library. i have followed the https://github.com/reaper-oss/sws/wi...-SWS-Extension with spliting it into two different folders but when i open the project inside the sws folder, i can't reference the library. Can anyone help me please?

cfillion 10-10-2018 08:10 AM

You need to have both the WDL and sws repositories cloned in the same parent directory (as described under the "File structure notes" section in the wiki page you linked). You should find a WDL subfolder in the WDL folder.

Dizzee 10-10-2018 08:15 AM

Quote:

Originally Posted by cfillion (Post 2044046)
You need to have both the WDL and sws repositories cloned in the same directory (as described under the "File structure notes" section in the wiki page you linked). You should have a WDL subfolder in the WDL folder.

What i have atm is a folder with two folders inside. One called sws with all the sws files and then another named WDL with the WDL library. To start it, i am opening the folder on VS. After that i don't know what is the next step

cfillion 10-10-2018 08:20 AM

Your directory structure sounds correct. If I understand correctly, you have opened the .vcxproj project file in Visual Studio (which version?), started the build and it complains it can't find some files from WDL? Please copy/paste the exact error messages.

Dizzee 10-10-2018 08:32 AM

Your directory structure sounds correct. If I understand correctly, you have opened the .vcxproj project file in Visual Studio (which version?), started the build and it complains it can't find some WDL files? Please copy/paste the exact error messages

I am using the VS2017, the latest. I am getting "Error MSB8020 The build tools for v120 (Platform Toolset = 'v120') cannot be found. To build using the v120 build tools, please install v120 build tools. Alternatively, you may upgrade to the current Visual Studio tools by selecting the Project menu or right-click the solution, and then selecting "Retarget solution"" and many undentified and not allowed

cfillion 10-10-2018 08:41 AM

This has nothing to do with WDL. You are seeing this message because the project was made for VS2013. Do the "Retarget solution" it suggests.

SWS can be made to build fine with VS2017 (that's what I use too) but be aware WDL's JNetLib needs to be patched for it (otherwise the SWS auto-update feature won't work properly): https://github.com/cfillion/WDL/comm...82ad08d2.patch.

Also the sws repository contains pre-built versions of TagLib (a bad idea in my opinion, but I digress...). You'll either need to go through the trouble of rebuilding it with VS2017 or just add NO_TAGLIB to the pre-processor definitions to disable that feature entirely.

Dizzee 10-10-2018 08:51 AM

I have done the retarget recomended and i have patched it on the netinc.h file. The rebuilding part i do not understand sorry. Could you explain it please?


All times are GMT -7. The time now is 09:35 PM.

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2018, vBulletin Solutions Inc.