any chance to support some @ var to help for releasing for both classic and bfa from the same code base ?
specifically I would like:
##Interface: @latest_retail_and_classic@
that would auto build the package twice, once with 80200 and once with 11302 (at the time of this writing), create 2 zip
MyAddon-mytag.zip and MyAddon-mytag-classic.zip with the right toc inside and the right label for finding with twitch app/curse download
(I made sure my code has the right ifs to work for both but now each time I make a change I have to make 2 extra commits just to tag with the new interface)
Took me a while searching around I found this thread... here is a working minimal version of the above without unnecessary noise
it doesn't quite answer the OP's question though, on how to set a multi line edit box without a scroll bar, but can be useful for others (works when pasted in /lua wowlua addon; every line is necessary for it to work)
local s = CreateFrame("ScrollFrame", nil, UIParent, "UIPanelScrollFrameTemplate") -- or you actual parent instead s:SetSize(300,200) s:SetPoint("CENTER") local e = CreateFrame("EditBox", nil, s) e:SetMultiLine(true) e:SetFontObject(ChatFontNormal) e:SetWidth(280) -- 300 - 20 or so for scroll bar s:SetScrollChild(e) --- demo multi line text e:SetText("line 1\nline 2\nline 3\nmore...\n\n\n\n\n\nanother one\n" .."some very long...dsf v asdf a sdf asd df as df asdf a sdfd as ddf as df asd f asd fd asd f asdf LONG LINE\n\n\nsome more.\nlast!") e:HighlightText() -- select all (if to be used for copy paste) -- optional/just to close that frame e:SetScript("OnEscapePressed", function() s:Hide() end)
Ping. I need a way to switch interface version and release the same add on for both with the only difference being the ## Interface line, unless someone can convince blizzard they need wow.exe to understand multiple interface lines or coma separated one
There is now an option to set compatibility for both Classic and Retail in the file upload.
However, its currently broken. It generates an internal server error if you don't choose that it is compatible with BOTH. (ie, you must pick a version in each, and not just one or the other)
Thanks - do you have a link to that doc/attribute ? (ie how to do that with the automatic git tag->build system vs that manual file upload)
How does curse and the twitch client plan to handle addon versions for Classic vs retail ?
I'd like to know how to maintain my addons and also what others plan to do to have both a live and a classic version ? (branching in git seems the way to go but... how to push more than 1 version to curse...)
0
I switched to github actions to build and push both classic and bfa versions automatically:
eg
https://github.com/mooreatv/NeatMinimap/blob/master/.github/workflows/packaging.yaml
0
storm- can you point to your addon being built by curseforge on a branch? (maybe they fixed it since I tried it a couple of weeks back)
0
branches will mess up the curse builder yes (you may even not be able to build anything new, after you make one, from my experience)
what I do now is:
https://github.com/mooreatv/AuctionDB/blob/master/classictag.sh
but it's quite ugly (and would be even more ugly if you needed 2 branches)
the BigWigs packager has a way to do a better job
0
If I were you I'd import my subversion repo into GitHub and move away from klunky wowace cf (sort of) supported infra.
Discover a modern UI, good workflow etc... and go with GitHub - the import preserve all the history and there is no looking back
0
yes I agree blizzard supporting multiple lines or multiple versions on the one line would be the easiest/best for everyone
0
concrete proposal... https://authors.curseforge.com/forums/world-of-warcraft/general-chat/updaters/240327-classic-vs-bfa-interface-toc-versions
it'd be nice those forums would get some kind of answers from CF ?
1.54714362449296
any chance to support some @ var to help for releasing for both classic and bfa from the same code base ?
specifically I would like:
##Interface: @latest_retail_and_classic@
that would auto build the package twice, once with 80200 and once with 11302 (at the time of this writing), create 2 zip
MyAddon-mytag.zip and MyAddon-mytag-classic.zip with the right toc inside and the right label for finding with twitch app/curse download
(I made sure my code has the right ifs to work for both but now each time I make a change I have to make 2 extra commits just to tag with the new interface)
0
Took me a while searching around I found this thread... here is a working minimal version of the above without unnecessary noise
it doesn't quite answer the OP's question though, on how to set a multi line edit box without a scroll bar, but can be useful for others (works when pasted in /lua wowlua addon; every line is necessary for it to work)
0
or not?
0
Ping. I need a way to switch interface version and release the same add on for both with the only difference being the ## Interface line, unless someone can convince blizzard they need wow.exe to understand multiple interface lines or coma separated one
0
Quote from DahkCeles >>
Thanks - do you have a link to that doc/attribute ? (ie how to do that with the automatic git tag->build system vs that manual file upload)
0
Hi there,
How does curse and the twitch client plan to handle addon versions for Classic vs retail ?
I'd like to know how to maintain my addons and also what others plan to do to have both a live and a classic version ? (branching in git seems the way to go but... how to push more than 1 version to curse...)
Thanks