- Joined
- Jul 30, 2013
- Messages
- 225
- Reaction score
- 425
- First Language
- English
- Primarily Uses
- RMMV
Description of the Feature:
Implementation:
While I don't know what the code looks like, I'm fairly certain adding another type of parameter shouldn't be too much trouble after so many have been added already. Furthermore, QT already has the capability to create a color input dialog:
http://doc.qt.io/qt-4.8/qcolordialog.html
The dialog returns a QColor object that contains a method for obtaining the red, green, and blue of the color.
Simply throw those values into a CSS color string, "rgb(x, x, x)", and it's ready to be throw into the parameter data.
Mockup:
Why is this feature good?
There are tons of plugins that already have users input colors through Window.png Codes or HEX/HTML Format, both of which require users to rely upon external references in order to select the color they desire. This makes things extremely frustrating and is likely to result in human error. Being able to view and customize the color straight from the parameters would help immensely.
Here's a list of a couple existing plugins I managed to throw together that ask for color input within the parameters:
Possible issues with this feature?
I cannot imagine any issues that may arise, aside from plugin developers having to tweak old plugins in order to use the new parameter type.
- This would be a feature that adds the capability for plugin developers to set up parameters to use a "Color" input type.
- The parameter would function by having the users open the parameter, click a button to open the color picker, customize the color, and return once complete.
- It would also have a preview of the color beside the button, allowing users to view what they selected without much trouble.
Implementation:
While I don't know what the code looks like, I'm fairly certain adding another type of parameter shouldn't be too much trouble after so many have been added already. Furthermore, QT already has the capability to create a color input dialog:
http://doc.qt.io/qt-4.8/qcolordialog.html
The dialog returns a QColor object that contains a method for obtaining the red, green, and blue of the color.
Simply throw those values into a CSS color string, "rgb(x, x, x)", and it's ready to be throw into the parameter data.
Mockup:
Why is this feature good?
There are tons of plugins that already have users input colors through Window.png Codes or HEX/HTML Format, both of which require users to rely upon external references in order to select the color they desire. This makes things extremely frustrating and is likely to result in human error. Being able to view and customize the color straight from the parameters would help immensely.
Here's a list of a couple existing plugins I managed to throw together that ask for color input within the parameters:
YEP_CoreEngine.js
YEP_ClassChangeCore.js
YEP_BuffsStatesCore.js
YEP_AbsorptionBarrier.js
YEP_EnhancedTP.js
YEP_EquipBattleSkills.js
YEP_GabWindow.js
YEP_KeyboardConfig.js
YEP_MessageCore.js
YEP_PartySystem.js
YEP_SkillCore.js
YEP_StatusMenuCore.js
YEP_VictoryAftermath.js
YEP_X_BattleSysATB.js
YEP_X_BattleSysCTB.js
YEP_X_BattleSysSTB.js
YEP_X_EquipRequirements.js
YEP_X_EventChaseStealth.js
YEP_X_ItemDurability.js
YEP_X_LimitedSkillUses.js
YEP_X_PartyLimitGauge.js
YEP_X_SkillCooldowns.js
YEP_X_SkillCostItems.js
YEP_X_Subclass.js
YEP_X_TurnOrderDisplay.js
YEP_X_VisualHpGauge.js
GALV_ManualLevel.js
GALV_CustomTitle.js
QuasiDepths.js
QuasiMovement.js
QuasiPopup.js
QuasiDepths.js
WindowIdentifier.js
cellicom_RarityItemColor.js
MrTS_ColorShiftingEnemies.js
MrTS_Crafting.js
MrTS_ItemColors.js
MrTS_QuestLog.js
MrTS_SimpleItemTracking.js
MrTS_StatesEX.js
MrTS_HPMPTPMulticolorGauges
YEP_ClassChangeCore.js
YEP_BuffsStatesCore.js
YEP_AbsorptionBarrier.js
YEP_EnhancedTP.js
YEP_EquipBattleSkills.js
YEP_GabWindow.js
YEP_KeyboardConfig.js
YEP_MessageCore.js
YEP_PartySystem.js
YEP_SkillCore.js
YEP_StatusMenuCore.js
YEP_VictoryAftermath.js
YEP_X_BattleSysATB.js
YEP_X_BattleSysCTB.js
YEP_X_BattleSysSTB.js
YEP_X_EquipRequirements.js
YEP_X_EventChaseStealth.js
YEP_X_ItemDurability.js
YEP_X_LimitedSkillUses.js
YEP_X_PartyLimitGauge.js
YEP_X_SkillCooldowns.js
YEP_X_SkillCostItems.js
YEP_X_Subclass.js
YEP_X_TurnOrderDisplay.js
YEP_X_VisualHpGauge.js
GALV_ManualLevel.js
GALV_CustomTitle.js
QuasiDepths.js
QuasiMovement.js
QuasiPopup.js
QuasiDepths.js
WindowIdentifier.js
cellicom_RarityItemColor.js
MrTS_ColorShiftingEnemies.js
MrTS_Crafting.js
MrTS_ItemColors.js
MrTS_QuestLog.js
MrTS_SimpleItemTracking.js
MrTS_StatesEX.js
MrTS_HPMPTPMulticolorGauges
Possible issues with this feature?
I cannot imagine any issues that may arise, aside from plugin developers having to tweak old plugins in order to use the new parameter type.
Attachments
Last edited: