Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disable craftNext button while crafting #740

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

isthevao
Copy link

Updated the "Next: Craft" button behavior to disable while crafting is in progress.

This improvement makes it easier to monitor crafting progress, especially when managing multiple characters simultaneously on the same screen. It's a simple way to quickly identify whether the crafting process is active or has completed.

@@ -1603,7 +1603,8 @@ function CraftSim.CRAFTQ.UI:UpdateQueueDisplay()
local firstRow = queueTab.content.craftList.activeRows[1]
local craftButton = firstRow.columns[11].craftButton --[[@as GGUI.Button]]
local button = craftButton.frame --[[@as Button]]
queueTab.content.craftNextButton:SetEnabled(button:IsEnabled())
local isCrafting = C_TradeSkillUI.IsRecipeRepeating()
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just tested this api call: C_TradeSkillUI.IsRecipeRepeating()
It seems to be only true if the recipe is crafted with a count of more than 2
If its just crafted once it returns false

Maybe there is another api call to be used here?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I couldn't find another API call for this. Indeed, when I click "Next: Craft," the button only disables after the second craft.
Maybe registering an event on button click?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Ready
Development

Successfully merging this pull request may close these issues.

2 participants