c# - Why is System.ComponentModel.AttributeCollection indexer inconsistent? -


in reference system.componentmodel.attributecollection.this[type t] indexer, docs @ http://msdn.microsoft.com/en-us/library/yadycs8s.aspx following

if attribute not exist in collection, property returns default value attribute type.

with in mind following code works expected: (> represents output)

using system.componentmodel; var attrcollection = new attributecollection(); console.writeline(attrcollection[typeof(browsableattribute)] != null); > "true"

prints "true" expect. trying random attribute debuggerdisplay, indexer returns null:

var attrcollection = new attributecollection(); console.writeline(attrcollection[typeof(system.diagnostics.debuggerdisplayattribute)] != null); > "false"

any ideas on different between these attributes, causing different behavior? unclear me msdn means 'default value attribute type' not null. thought perhaps problem attribute type no parameterless constructor, browsableattribute requires 1 argument, debuggerdisplayattribute.

it explicitly documented in msdn library article attributecollection:

while attributes have default values, default values not required. if attribute has no default value, null returned indexed property takes type. when defining own attributes, can declare default value either providing constructor takes no arguments, or defining public static field of attribute type named "default".

browsableattribute has such default value, provided default field, test succeeds. makes class members browsable default when attribute missing.

debuggerdisplayattribute has neither default constructor nor default field. makes sense if think it, there no meaningful default useful in debugger.


Comments

Post a Comment

Popular posts from this blog

Why does Ruby on Rails generate add a blank line to the end of a file? -

running rails generate controller foo home results in: class foocontroller < application controller def home end end (there's nothing on line in actual file, blank line) is there purpose blank line? it's common use newline indicate end of line, last line. many editors (like vi, use) add in newline silently. consensus text files (especially in unix world) should end in newline, , there have been problems historically if wasn't present. why should text files end newline? the tool used count lines in file "wc" counts newlines in file, without trailing newline show 3 instead of 4. it improves readability of templates used in generator. consider: https://github.com/rails/rails/blob/master/railties/lib/rails/generators/rails/controller/templates/controller.rb to remove trailing newline, template have last line of: end<% end -%> instead of: end <% end -%> that seems less readable me. the discussion below refers
Read more

keyboard - Smiles and long press feature in Android -

i've created android keyboard. how add features inserting smilies, , using long keypresses display symbols? to create long-press behavior allows select several options pop-up menu, follow guide (specifically pop-up menu section): http://developer.android.com/guide/topics/ui/menus.html smileys (also known emoticons) combination of keys, understood programs , parsed same way. have do, when clicks smiley face on keyboard, simulate pressing of key combination matching emoticon. example, when clicks smiley, should simulate key presses ':' , ')' :). here's list of emoticons: http://en.wikipedia.org/wiki/list_of_emoticons
Read more

node.js - Bad Request - node js ajax post -

i'm using express 3.0 , node v0.11.0. have button submits form , i'm using ajax post data json object node server. client code is: $('#contact').submit(function(e) { console.log('submit called'); var formdata = json.stringify($('form').serializeobject()); console.log(formdata); $.ajax({ url: "http://localhost:3000/savedata/", type: "post", datatype: 'json', data: {objectdata: formdata}, contenttype: "application/json", complete: function() { console.log('process complete'); }, success: function(data) { console.log('process sucess'); }, error: function() { console.log('process error'); }, }); return false; }); then on server: var express = require('express'); var app = express(); app.set('views', __dirname + '/views'); app.set('view engine', 'jade'); app.use(express.bodyparser());
Read more