Sponsored Content
Top Forums Web Development New Font Awesome Icons in Quick Reply Editor Post 303027024 by Neo on Friday 7th of December 2018 07:09:17 AM
Old 12-07-2018
Update: Was able to find an acceptable NOPARSE font Font Awesome in the Quick Reply Editor.

TODO: Need to change the "advanced" and "edit post" editors.... Will do this TODO after the QRE is done.
These 4 Users Gave Thanks to Neo For This Post:
 

6 More Discussions You Might Find Interesting

1. What is on Your Mind?

New jQuery to view Post Icons in Editor

I was reformatting the "advanced" WYSIWYG editor with bootstrap css and while there made the post icons to be invisible by default; so if you click on the text below the editor: Post Icons - Click to view the full list of message icons to add to your post: ... (0 Replies)
Discussion started by: Neo
0 Replies

2. What is on Your Mind?

New Icons Coming from Font Awesome

Finally making some progress on getting rid of the 10 year old buttons with modern day fonts and icons thanks to a responsive web design tutorial by Brad Traversy who's video pointed me to Font Awesome. The buttons and icons were pretty easy to implement but it too me a number of hours... (39 Replies)
Discussion started by: Neo
39 Replies

3. What is on Your Mind?

Small bug in the Quick Editor function in postbit

Hey, There was a small bug in the Quick Editor function in postbit, but I fixed it (basically a double quote was missing from an element id): <div id="post_message_$post" class="neo-message-area">$post</div> Was <div id="post_message_$post class="neo-message-area">$post</div> Should... (1 Reply)
Discussion started by: Neo
1 Replies

4. What is on Your Mind?

New Mobile Navbar Icons from Font Awesome

Just changed the mobile site to use Font Awesome icons. Here is the new top navbar view (unregistered users) https://www.unix.com/members/1-albums214-picture903.jpeg (2 Replies)
Discussion started by: Neo
2 Replies

5. What is on Your Mind?

Quick Update on UNIX.COM Site Renovation: Bootstrap, Font Awesome and jQuery

Here is an update on the site renovation: After a lot of analysis and example programming, including testing out a number of Javascript framework and libraries, in the short term, we are getting the most bang-for-the-buck from these three basic, core tech areas: Bootstrap (CSS and... (2 Replies)
Discussion started by: Neo
2 Replies

6. What is on Your Mind?

New CODE and ICODE Editor Button Icons

As promised, I have changed the CODE tag icon and the ICODE tag icon in our WYSIWYG editors to use Font Awesome. CODE Tag = fa-code ICODE Tag = fa-terminal https://www.unix.com/members/1-albums215-picture966.png The reason for this change is to continue our move toward Font Awesome... (4 Replies)
Discussion started by: Neo
4 Replies
xcb_xkb_per_client_flags(3)					   XCB Requests 				       xcb_xkb_per_client_flags(3)

NAME
xcb_xkb_per_client_flags - SYNOPSIS
#include <xcb/xkb.h> Request function xcb_xkb_per_client_flags_cookie_t xcb_xkb_per_client_flags(xcb_connection_t *conn, xcb_xkb_device_spec_t deviceSpec, uint32_t change, uint32_t value, uint32_t ctrlsToChange, uint32_t autoCtrls, uint32_t autoCtrlsValues); Reply datastructure typedef struct xcb_xkb_per_client_flags_reply_t { uint8_t response_type; uint8_t deviceID; uint16_t sequence; uint32_t length; uint32_t supported; uint32_t value; uint32_t autoCtrls; uint32_t autoCtrlsValues; uint8_t pad0[8]; } xcb_xkb_per_client_flags_reply_t; Reply function xcb_xkb_per_client_flags_reply_t *xcb_xkb_per_client_flags_reply(xcb_connection_t *conn, xcb_xkb_per_client_flags_cookie_t cookie, xcb_generic_error_t **e); REQUEST ARGUMENTS
conn The XCB connection to X11. deviceSpec TODO: NOT YET DOCUMENTED. change TODO: NOT YET DOCUMENTED. value TODO: NOT YET DOCUMENTED. ctrlsToChange TODO: NOT YET DOCUMENTED. autoCtrls TODO: NOT YET DOCUMENTED. autoCtrlsValues TODO: NOT YET DOCUMENTED. REPLY FIELDS
response_type The type of this reply, in this case XCB_XKB_PER_CLIENT_FLAGS. This field is also present in the xcb_generic_reply_t and can be used to tell replies apart from each other. sequence The sequence number of the last request processed by the X11 server. length The length of the reply, in words (a word is 4 bytes). deviceID TODO: NOT YET DOCUMENTED. supported TODO: NOT YET DOCUMENTED. value TODO: NOT YET DOCUMENTED. autoCtrls TODO: NOT YET DOCUMENTED. autoCtrlsValues TODO: NOT YET DOCUMENTED. DESCRIPTION
RETURN VALUE
Returns an xcb_xkb_per_client_flags_cookie_t. Errors have to be handled when calling the reply function xcb_xkb_per_client_flags_reply. If you want to handle errors in the event loop instead, use xcb_xkb_per_client_flags_unchecked. See xcb-requests(3) for details. ERRORS
This request does never generate any errors. SEE ALSO
AUTHOR
Generated from xkb.xml. Contact xcb@lists.freedesktop.org for corrections and improvements. XCB
2014-06-10 xcb_xkb_per_client_flags(3)
All times are GMT -4. The time now is 05:18 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy