Wonder if someone can help?
I'm trying to cap a mark for an assignments spreadsheet if it is submitted late, or the attempt is more than 1. One exception is that it is submitted late, however their assignment was "Accepted - Late". I have checked all the references and all seem to be OK. It is not capping if G4 is blank but E4 is larger than F4, but it should and I can't see why it won't here.
As far as I can tell:
(is the work late (E4>F4)
AND is it Accepted late) if so, keep below 101, if not check if the work is late, if it is late then cap at 50, if not, check if attempt is more than 1, if it is cap at 50, if not cap at 101.
=IF(AND($E4>$F4, $G4="Accepted - Late"), $J4<101, IF($E4>$F4, $J4<51, IF($B4>1, $J4<51, $J4<101)))
After changing some formatting, this seemed to work, note some columns moved around.
=IF(AND($D3>$E3, F3="Accepted - Late"), $I3<101,IF(K3>1, $I3<41, IF($D3>$E3, $I3<41,$I3<101)))
Related
I was experimenting in VPython with my scene's camera and I discovered that scene.camera.pos is always equal to <0, 0, 1.73205> and scene.camera.axis is always equal to <0, 0, -1.73205>. These values don't change even when the camera auto-adjusts or when I use the scene.camera.follow function. Why is that? Also, I am able to change these values. However, for the scene.camera.pos it seems like going below 1 doesn't change anything from setting it to one. This is really odd and I hope someone can clear it up for me.
This has been addressed in the VPython forum:
https://groups.google.com/g/vpython-users
Working on a payroll integration sheet for a tiered payroll structure. I have rearranged to allow for IF and THEN structure, tried as IF condition for validation only. Bending my eyes around this and hoping someone can prodigy this quickly without losing my mind today. I know im overlooking it, whos got fast eyes here. enter image description here
original:
=IF(AND(C26<23.9),(C26=24-31.9),(C26=32-39.9),(THEN(B26*11,B26*12,B26*13,B26*14)))
TBH, this is a bit of a cystal ball prediction but it seems you are looking to return different values based on C26 being within one of three ranges or another if outside all 3.
The literal translation would be,
=if(C26<24, B26*11, if(and(C26>=24, C26<32), B26*12, if(and(C26>=32, C26<40), B26*13, B26*14)))
However, this can be tightened up by reversing the flow of logic and only returning B26's modifier..
=B26*if(C26>=40, 14, if(C26>=32, 13, if(C26>=24, 12, 11)))
Further formula adjustment might produce,
=B26*lookup(C26, {0, 24, 32, 40}, {11, 12, 13, 14})
The newer IFS function would look like,
=B26*ifs(C26>=40, 14, C26>=32, 13, C26>=24, 12, TRUE, 11)
One final attempt using booleans for addition,
=B26*(11+(C26>=24)+(C26>=32)+(C26>=40))
Use this:
=(MATCH(C26,{-1E+99,24,32,40})+10)*B26
Or if you have OFFICE 365 Excel:
=IFERROR(IFS(C26>=40,14,C26>=32,13,C26>=24,12),11)*B26
I searched around on this site and found something similar to what I need, but I haven't been able to get it to work for me yet. I was able to get it to work when I do only half of it, but when I try to work in the other 2 conditions with AND statements, it gets messed up and I can't figure out what's going wrong.
The partial string of code that worked for me is this
=IF(M7>O7, IF(P7="R", 3, IF(P7="O", 2, IF)))
I have statements that would give different output...
If m7>o7 and p7="R" output a value of 3
If m7>o7 and p7="O" output a value of 2
If o7>m7 and p7="O" output a value of 1
If o7>m7 and p7="R" output a value of 0
Thanks in advance!
=IF(M7>O7,IF(P7="R",3,2),IF(P7="R",0,1))
Per the comment:
=IF(AND(M7<>"",O7<>"",P7<>""),IF(M7>O7,IF(P7="R",3,2),IF(P7="R",0,1)),"")
Currently, I made a tool to rename view numbers (“Detail Number”) on a sheet based on their location on the sheet. Where this is breaking is the transactions. Im trying to do two transactions sequentially in Revit Python Shell. I also did this originally in dynamo, and that had a similar fail , so I know its something to do with transactions.
Transaction #1: Add a suffix (“-x”) to each detail number to ensure the new numbers won’t conflict (1 will be 1-x, 4 will be 4-x, etc)
Transaction #2: Change detail numbers with calculated new number based on viewport location (1-x will be 3, 4-x will be 2, etc)
Better visual explanation here: https://www.docdroid.net/EP1K9Di/161115-viewport-diagram-.pdf.html
Py File here: http://pastebin.com/7PyWA0gV
Attached is the python file, but essentially what im trying to do is:
# <---- Make unique numbers
t = Transaction(doc, 'Rename Detail Numbers')
t.Start()
for i, viewport in enumerate(viewports):
setParam(viewport, "Detail Number",getParam(viewport,"Detail Number")+"x")
t.Commit()
# <---- Do the thang
t2 = Transaction(doc, 'Rename Detail Numbers')
t2.Start()
for i, viewport in enumerate(viewports):
setParam(viewport, "Detail Number",detailViewNumberData[i])
t2.Commit()
Attached is py file
As I explained in my answer to your comment in the Revit API discussion forum, the behaviour you describe may well be caused by a need to regenerate between the transactions. The first modification does something, and the model needs to be regenerated before the modifications take full effect and are reflected in the parameter values that you query in the second transaction. You are accessing stale data. The Building Coder provides all the nitty gritty details and numerous examples on the need to regenerate.
Summary of this entire thread including both problems addressed:
http://thebuildingcoder.typepad.com/blog/2016/12/need-for-regen-and-parameter-display-name-confusion.html
So this issue actually had nothing to do with transactions or doc regeneration. I discovered (with some help :) ), that the problem lied in how I was setting/getting the parameter. "Detail Number", like a lot of parameters, has duplicate versions that share the same descriptive param Name in a viewport element.
Apparently the reason for this might be legacy issues, though im not sure. Thus, when I was trying to get/set detail number, it was somehow grabbing the incorrect read-only parameter occasionally, one that is called "VIEWER_DETAIL_NUMBER" as its builtIn Enumeration. The correct one is called "VIEWPORT_DETAIL_NUMBER". This was happening because I was trying to get the param just by passing the descriptive param name "Detail Number".Revising how i get/set parameters via builtIn enum resolved this issue. See images below.
Please see pdf for visual explanation: https://www.docdroid.net/WbAHBGj/161206-detail-number.pdf.html
Is it in anyway possible to increase the number of suggests that your extension may show in the omnibox?
By default it looks like 5 rows is the limit. I've read about a command line switch to change the number of rows (--omnibox-popup-count) but I am really interested in dynamically being able to set this in my extension.
5 rows isn't really enough for the information my extension want to show.
[Update 2018 - thanx version365 & Aaron!]
» Not hardcoded anymore! chrome://flags/#omnibox-ui-max-autocomplete-matches . Credit goes to #version365 answering below: http://stackoverflow.com/a/47806290/234309 « – Aaron Thoma
..[historical] detail: since the removal of --omnibox-popup-count flag (http://codereview.chromium.org/2013008) in May 2010 the number [was] hardcoded:
const size_t AutocompleteResult::kMaxMatches = 6;
a discussion two years later on the chromium-discuss mailing list about the 'Omnibox default configuration' "concluded"
"On lower performing machines generating more result would slow down the result display. The current number look like a good balance."
[which is not a very valid argument, considering the probably infinitesimal overhead retrieving more items than the hard-wired number]
why the heck is there no chromium fork that removes stupid UX limitations like this (or the no tabbar in fullscreen mode)^^
Since there is no more --omnibox-popup-count flag; you can use another flag which is new.
chrome://flags/#omnibox-ui-max-autocomplete-matches lets you select a maximum of 12 rows.
In fact there is no more --omnibox-popup-count flag
http://code.google.com/p/chromium/issues/detail?id=40083
So I think there is no way to enlarge the omnibox.