SolarStrike Software

lisa wrote:I find the green hard to read, White is very easy to read but there is already so much of it with it being skills used.
I hadn't really put any thought into redoing the colour scheme but for me personally I'd change the skills to not white and have things that I want to grab my attention to be white.

rock5 wrote:Administrator suggests user settings so the user can change the colors.
Something like;

Code: Select all

["MESSAGE_COLOR_ERROR"] = cli.red,
["MESSAGE_COLOR_WARNING"] = cli.yellow,
["MESSAGE_COLOR_STANDARD"] = cli.green,

I still think we could review the default colors used.

I think we need to define a system of levels. Something like;
error = lightred
warning = yellow
skilluse = lightgray

Maybe multiple levels of info colors
infolow = green
infomedium = lightgreen
info high = lightblue

Then decide what color messages should use. The least important and often never read messages should use infolow. Messages that still come out often but are a bit more important should be info medium. Maybe 'move to waypoint' messages fall in this category. Messages that don't come out often and are more important would use infohigh, messages like loading waypoint file or reversing direction or using a function to changes a setting. You get the idea.

function printbot(msg,type,ingame)
local color;
local colorStr;

if not msg then
  return
end

-- define colors
if type == "warning" then
   color = cli.yellow;
   -- colorStr =   some code for ingame chat color system
end
-- and so on... ... ..
if not type then
  color = cli.white
  colorStr = ""
end

if ingame then
   --code to print in game chat using colorStr
end

cprintf(color,msg);

end

printbot(msg[,type,ingame]);

rock5 wrote:I like it but I'm not sure about mixing ingame and MM. Mainly because it could cause confusion but also because the colors you would use in the mm window would not necessarily be the same as you would use ingame.

The idea here would be that some people (I at least) would like some information to be presented on the client. For example I print my daily quests count in both MM and client.
Keeping the colors the same was only a matter of coherence between MM and game chat window.

rock5 wrote: Also I'm not sure of the function name. Maybe 'printMSG'?

printBot was an example we can use whatever. what about 'Text(msg,type)'?

rock5 wrote:Then again, whats the difference between printf(type,msg) and printbot(msg,type) ?

rock5 wrote:What I meant by "whats the difference between printf(type,msg) and printbot(msg,type) ?" is they are both just as easy to write and function the same (besides the arguments being reversed).

So the only reason to have the printbot function is so you can optionally write to the client but like I said I don't like using 1 function to do both.

So why not use

Code: Select all

printf(settings.MESSAGE_COLOR_ERROR,"Unable to read memory!") 

when writing to the mm window.

And have another function for writing to the client. You could also add other messaging options besides color like the options used with SendChatMessage

Still not convinced?